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

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