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

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