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

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