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

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