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

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