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

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