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

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