Difference naming conventions across different db technologies

[Former Member]

Hi,

I'm creating a database schema for use across

     MS-SQL, Postgres and Sybase ASE

We already have some tables in Sybase following CamelCase (Pascal case to be specific)

which we can't create in db's which are case insensitive.

Is there a way we can create a model with one set of table namings but generate a model which generates a different set of namings

eg

     UPLOAD_CONTROL is left untouched for MS-SQL and becomes UploadControl when creating for Sybase ?

or

     UploadControl  is left untouched for ASE and becomes UPLOAD_CONTROL when creating for MS-SQL

[Former Member]

Or you can keep your model in LDM and generate appropriate target PDMs for different DBs with different naming convention setting.

Or you can define extended attributes for keeping different CASE of names and a simple script, which will exchange the name from your extended attribute with the code of the object just prior to the DB generation.

[GeorgeMcGeachie]

Hmm, in a Transformation you could probably apply different naming conventions depending on the DBMS. A little tricky do, 'cos the Model options are held as a single string, I think.