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

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