One Response to The G/Technology developer experience

  1. bnewfelt says:

    GPT is a good starting point for building new features, but the saved sql generated must be edited to provide logical feature numbers and names. Once the sql scripts have been run in your development schema, changes are easy to make through Metadata Explorer. Having a template script to pull the table data from the development schema allows the feature definitions to be migrated to a QA schema and eventually a production schema. For instance, this sql will generate the insert statement for the G3E_FEATURE table:

    select ‘INSERT INTO G3E_FEATURE (G3E_FNO, G3E_USERNAME, G3E_TOOLTIP, G3E_PRIMARYGEOGRAPHICCNO, G3E_PRIMARYATTRIBUTECNO, G3E_DCNO, G3E_PRIMARYDETAILCNO, G3E_NUMBEROFNODES, G3E_IMPORTFEATURENAME, G3E_REPLACE, G3E_NAME, G3E_MERGE, G3E_CLASSIFICATIONANO, G3E_IDENTIFIERVIEW, G3E_BULKEDIT , G3E_ICONORDINAL, G3E_EDITROLE, G3E_SELECTROLE, G3E_DELETEROLE, G3E_RINO, G3E_RIARGGROUPNO, G3E_EDITDATE)
    ‘ || ‘
    VALUES(‘ || G3E_FNO || ‘,”’ || G3E_USERNAME || ”’,”’ || G3E_TOOLTIP || ”’,”’ ||
    G3E_PRIMARYGEOGRAPHICCNO || ”’,”’ || G3E_PRIMARYATTRIBUTECNO || ”’,”’ || G3E_DCNO || ”’,”’ || G3E_PRIMARYDETAILCNO || ”’,”’ || G3E_NUMBEROFNODES || ”’,”’ || G3E_IMPORTFEATURENAME || ”’,”’ || G3E_REPLACE || ”’,”’ || G3E_NAME || ”’,”’|| G3E_MERGE || ”’,”’ || G3E_CLASSIFICATIONANO || ”’,”’ || G3E_IDENTIFIERVIEW || ”’,”’ || G3E_BULKEDIT || ”’,”’ || G3E_ICONORDINAL || ”’,”’ || G3E_EDITROLE || ”’,”’ || G3E_SELECTROLE || ”’,”’ || G3E_DELETEROLE || ”’,”’ || G3E_RINO || ”’,”’ || G3E_RIARGGROUPNO || ”’,SYSDATE);’
    from G3E_FEATURE
    where G3E_FNO in (100, 200, 300)
    order by G3E_FNO;

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>