1
Suggestions and Requests / Re: IDEA: Better FK constraint naming rule
« on: May 07, 2007, 02:59:45 am »
FK naming is surely a destination platform specific issue, for example, a defaulting name that uses upper case prefixing is just not going to work in postgresql.
There should be a way to specify how Enterprise Architect names any specially or automatically created item, especially if that has or could have downstream impacts. EA should provide a destination platform specific naming convention, just like it does for platform specific attributes e.g int v integer, date v datetime, etc etc.
I have just been caugt out on the same issue that the original poster was indicating. EA kept overwriting the 5 FK's with a single one because of this silly naming convention. ... I only picked it because I have to go through the DDL script, all 1112 lines, every time and convert all the ' fk ' names to lower case.
I'm beginning to think this isn't all it's supposed to be.
Sandy
There should be a way to specify how Enterprise Architect names any specially or automatically created item, especially if that has or could have downstream impacts. EA should provide a destination platform specific naming convention, just like it does for platform specific attributes e.g int v integer, date v datetime, etc etc.
I have just been caugt out on the same issue that the original poster was indicating. EA kept overwriting the 5 FK's with a single one because of this silly naming convention. ... I only picked it because I have to go through the DDL script, all 1112 lines, every time and convert all the ' fk ' names to lower case.
I'm beginning to think this isn't all it's supposed to be.
Sandy