Gen EDGE

 View Only

  • 1.  Implementation of TIMESTAMP in Oracle vs. DB2

    Posted Jan 25, 2016 01:05 PM

    Hello again!  Wow, I keep finding differences in the TD when trying to switch from DB2 to Oracle.  So from one of the last issues I brought up, we are having to switch all non-identifying attributes from Mandatory to Optional, and then setting the default value in order to get the proper DDL generated.  That is working fine.  However, because I have to retransform in order to implement "optional" as null, that is now taking all of my TIMESTAMP attributes and selecting a default of DATE rather than TIMESTAMP when doing the implementation.  I have found that I can go in and reset it column by column here, but was hoping there is some higher level property to tell the transformation to choose TIMESTAMP as the default.  Anyone know how???

     

    OracleTS.PNG



  • 2.  Re: Implementation of TIMESTAMP in Oracle vs. DB2

    Posted Jan 25, 2016 03:13 PM

    doucet.cathy I don't think that there currently is a way to give transformation any clues as to how it should transform timestamp attributes when targetting Oracle.  This might be a good thing to add to the Ideas site on the community as there might be a number of different things that could be user-defaulted like that.  There is currently a Model Preferences value (Model / Settings / Model Preferences) that allows users to decide whether to transform text > 4000 characters into VARCHAR rather than LONG VARCHAR (the default) for DB2.  This preference (and others) could be implemented in a similar manner.



  • 3.  Re: Implementation of TIMESTAMP in Oracle vs. DB2

    Broadcom Employee
    Posted Jan 26, 2016 05:09 PM

    Hi Cathy/John,

    This should help:

    Since Gen started supporting the Oracle Timestamp data type a newly implemented Timestamp attribute will get a Timestamp data type.

    Before Gen supported the Oracle Timestamp data type the Timestamp attribute would be set as a Date data type.

     

    So to force the use of Timestamp data type on an older implemented Timestamp  attribute you basically need to reimplement the attribute & either of these options should work:

    • EITHER delete the Data Structure List for Oracle entirely and do a complete Transformation
    • OR if you use Retransformation with "Specialize TD for current DBMS" that should also force it.

     

    Hope this helps

     

    Regards,

     

    Lynn



  • 4.  Re: Implementation of TIMESTAMP in Oracle vs. DB2

    Posted Jan 26, 2016 06:28 PM

    Many thanks Lynn!!!!  I tried the retransform option and it worked, so we are happy!  :-)