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

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