View Only
Expand all | Collapse all

Targetting 'not-supported' DBMs with jdbc and

  • 1.  Targetting 'not-supported' DBMs with jdbc and

    Posted Sep 24, 2018 05:04 AM



    Our firm is considering migrating our database to some free dbms (probably PostgreSQL)


    Technically, PostgreSQL is not a supported database. However, you can configure the in order to make it work.


    I'm wondering if somebody has already go into that direction and has migrated to some other DB which is not one of the supported DBs (oracle, db2, mssql) and is willing to share some knowledge and experience, and some problems you could face on the process.


    Thanks a lot.

  • 2.  Re: Targetting 'not-supported' DBMs with jdbc and

    Posted Sep 27, 2018 01:22 PM

    What version of Gen are you on?

  • 3.  Re: Targetting 'not-supported' DBMs with jdbc and

    Posted Oct 01, 2018 02:40 AM

    We are on GEN r8.5

  • 4.  Re: Targetting 'not-supported' DBMs with jdbc and

    Posted Oct 01, 2018 03:34 PM

    Ok,   I don't have experience with JDBC, rather ODBC.  Recently I was involved in doing an upgrade where in a previous version of Gen there had been native support for a particular DB and that was deprecated.  I tried defining it as an ODBC database and generating the code targeting ODBC, which worked for the most part.  There were some things that didn't line up.  For those things I ended up using inline code statements in some called action blocks I created with only the inline code statements in it.


    This helped me around some of the incompatibility and we were able to deliver the required functionality.


    If you are not familiar with the Inline code statement, it was put in place in Gen 8.5 IE 1 to allow the developer to write complicated SQL statements or other code which Gen might not do.



    and related to ODBC/JDBC



    I have not Used JDBC in Gen, but I do expect that you might be able to have the connection managed by Gen and use inline code for anything that GEN might have a problem dealing with against the unsupported DBMS.


    I would not recommend using the unsupported DBMS as CA would not be involved if you needed further assistance.  Any help would come from this EDGE group, if they could provide it.


    What I would recommend is that you add an "IDEA" for JDBC Support for the DBMS you are wanting to work with. If it gets enough traction, it could be added to a future release of the product and then become "supported"


    I hope this helps

    Darcy Elliott