1 Reply Latest reply on Jun 5, 2020 12:11 PM by Dave Schleis

    Incorrectly generate DDL for column default value

    _Dima_

      Hello, it seems that Data Modeler does incorrectly generate DDL for column default value.

       

      I use SYSDATE as default value for column CREATED_AT. Data Modeler generates DDL with SYSDATE in lowercase. Thus I end up forever not synchronized model with actual schema, as in my model used SYSDATE and in schema 'sysdate'.

       

      Use Data Modeler 19.4, Oracle Base 12C, Oracle Linux 7.7

       

      Please see screenshots

       

      Screenshot from 2020-06-04 20-17-56.png

       

       

      Screenshot from 2020-06-04 20-18-22.png

       

       

       

      Screenshot from 2020-06-04 20-18-35.png

       

       

       

      Screenshot from 2020-06-04 20-18-51.png

       

       

      Did I make something wrong?

        • 1. Re: Incorrectly generate DDL for column default value
          Dave Schleis

          Hello,

           

          No, you did nothing wrong. I believe that the issue here is simply a preference setting.

           

          SQL Developer Data Modeler is amazingly customizable. There are preference settings at the application level, the design level and the model level.

           

          At the application level, one of the things you can set is what you want SDDM to pay attention to when comparing a relational model to a database instance.

          As you can see in the image below, one of these comparisons is case sensitivity.

           

          From the help:

          Case Sensitive Names in Compare Functionality: Controls whether the letter case in object names should be considered when comparing two objects

           

          I suspect that unchecking this comparison will make it easier for you to keep things in synch.

          Screen Shot 2020-06-05 at 6.57.52 AM.png

           

          Hope this helps

          --dave