Tech Articles


Defining a PostgreSQL Database Profile in PB2019R3


PB2019R3
PostgreSQL v12 database


Summary:
   Ensure that the database properties are defined correctly for the PostgreSQL database in the DB Painter.

   If those properties are not defined correctly, the PB2019R3 IDE automatically creates the PB Catalog tables in the "public" schema every time it connects to the PostgreSQL (PG) database even if the catalog tables are already defined in the named "PowerBuilder Catalog Table Owner" schema.

 

Details:
In our Oracle schemas, we have the PB Catalog table owner specified as the superuser CHADBA.


Once created in Oracle, the catalog tables are in the CHADBA schema.


The PB IDE opens up smoothly with NO prompt to "Create the PowerBuilder catalog tables."

~~~~~~~~~~~

We are in the process of migrating to PostgreSQL (PG).
 - PG is case sensitive, and in our case all table and columns names are in lower case.
 - Note: Users can migrate to an UPPER or a LOWER case copy. Choose the LOWER case to eliminate a variety of
            issues.

Our PG development database also has the PB catalog tables defined in the chadba schema.
We set up the PG database mostly in the same way we set up the Oracle databases; chadba is in lowercase:






Defined in this manner, the IDE opens up smoothly and does not give you the "PB catalog tables not available" message.

- - - - - - - - - - -

If the setup is NOT done correctly, then when I open PB2019R3 and the connection is to my dev12c_PG database, PowerBuilder creates the complete set of catalog tables in the public schema, but does not populate either of the new the EDT or FMT catalog tables.

Thus when I get into the DB Painter and "select * from pbcatfmt;" the result set is empty. Why? Because the new set of tables defined in "public" are overriding the set of tables previously defined in "chadba".

I have to manually delete the public.pbcat* tables ....

drop table public.pbcatcol;
drop table public.pbcattbl;
drop table public.pbcatfmt;
drop table public.pbcatvld;
drop table public.pbcatedt;
commit;

.... before I have access to the FMT and EDT data again:

-- pbcattbl, pbcatcol, pbcatfmt, pbcatvld, pbcatedt
//drop table public.pbcatcol;
//drop table public.pbcattbl;
//drop table public.pbcatfmt;
//drop table public.pbcatvld;
//drop table public.pbcatedt;
//commit;

select * from pbcatfmt;

 

 

Comments (0)
There are no comments posted here yet

Find Articles by Tag

PostgreSQL ODBC driver Elevate Conference InfoMaker JSONParser Data Platform WebBrowser ActiveX 32-bit PDF Messagging CrypterObject Expression Testing iOS Menu Web API Debugger JSON RichTextEdit Control Application Import JSON Database Object Windows OS Migration Database Profile Oracle UI Themes Installation TLS/SSL Encoding Interface Authentication Database Table Data SVN RibbonBar Service Event Handling Script Model Sort GhostScript IDE Event TFS PowerBuilder Compiler JSONGenerator MessageBox Source Code OAuth TortoiseGit Android SQL Debug Validation Charts SDK TreeView Configuration Performance Import DataWindow JSON Git Database Table Outlook Mobile Class .NET Std Framework Variable .NET DataStore ODBC Jenkins Trial CoderObject OLE PBVM RESTClient Export JSON Branch & Merge Graph DLL Excel External Functions Open Source SqlModelMapper PBNI License Icon Deployment Linux OS 64-bit Visual Studio UI Modernization File Database Bug Text PFC Error Event Handler PowerBuilder C# CI/CD Database Painter PowerServer Web Array Windows 10 Icons DataWindow RibbonBar Builder Repository SOAP XML REST PowerServer Mobile SnapObjects Source Control DragDrop Debugging Design API Syntax Web Service Proxy Azure SQL Server Automated Testing BLOB Authorization DataType UI Resize HTTPClient NativePDF .NET Assembly PowerBuilder (Appeon) Filter COM PDFlib Window PBDOM SnapDevelop WinAPI PostgreSQL PowerScript (PS) SqlExecutor Stored Procedure Database Connection Encryption OrcaScript Database Table Schema Export Transaction OAuth 2.0 DevOps