Attribute.CheckIdNameConflict
(Replacing message template with parser tag) |
(Updated Edited template to July 12, 2025.) |
||
| Line 11: | Line 11: | ||
This is a way to turn off the evolve feature (auto-evolve or the generate database). We usually warn the user that this name will be in conflict with the naming rules of the SQL server. If you are sure as a designer or developer that you want these names used anyway, you can set this to "false" and the evolve feature will use these probably conflicting names in your database. | This is a way to turn off the evolve feature (auto-evolve or the generate database). We usually warn the user that this name will be in conflict with the naming rules of the SQL server. If you are sure as a designer or developer that you want these names used anyway, you can set this to "false" and the evolve feature will use these probably conflicting names in your database. | ||
[[Category:Tagged Values]] | [[Category:Tagged Values]] | ||
{{Edited|July|12| | {{Edited|July|12|2025}} | ||
Latest revision as of 05:46, 20 January 2025
This page was created by Stephanie on 2023-05-18. Last edited by Edgar on 2025-01-20.
| #TargetType.TaggedValue | CommaSeparatedExampleValues | Short Description |
|---|---|---|
| #Attribute.CheckIdNameConflict | True,False | Avoids warning about naming conflicts between a table and the automatically named ID columns when generating an SQL database. |
This is a way to turn off the evolve feature (auto-evolve or the generate database). We usually warn the user that this name will be in conflict with the naming rules of the SQL server. If you are sure as a designer or developer that you want these names used anyway, you can set this to "false" and the evolve feature will use these probably conflicting names in your database.