Attribute.CheckIdNameConflict
m ((username removed) (log details removed): Moving to Documentation namespace) |
(Automatically adding template at the end of the page.) |
||
| Line 10: | Line 10: | ||
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|2024}} | |||
Revision as of 15:27, 10 February 2024
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.