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

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