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

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