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

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