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

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