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

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