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

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