This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
In the .NET framework properties and classes are not allowed to have the same name, so if a table's name and column match, this condition is violated by the designer. Example: I am not sure whether this is intentional (to let the developer resolve the conflict), but I guess for a nicer designer experience it might be nice to change the column name to something else to avoid a build error. This is also true for your autogenerated association names. If you happen to generate the same name this causes an error on save and although that might also be useful for someone to resolve the conflict manually it might be nicer to automatically generate unique names (maybe append a number?) |
|
|
|
|
You're right, this behaviour is by design. We believe is it better to signal the condition to the developer so that they can resolve it by giving the property or association a meaningful name, rather than hiding the problem behind a non-meaningful name. We believe developers will want to (and should) select a meaningful name, and the validation error alerts them that they need to do so. We do appreciate that some developers might prefer to defer selecting a meaningful name until after that initial save, so as always we are open to customer feedback on this. |
|
|
|
