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

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