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
|
Looks like when an underscore is in the Auto Through Entity property, and you update the data base everything is fine. However, in any subsequent update database attempt, it doesn't see the existing table and prompts that it is adding it again. Of course, this will fail, since it does actually exist. Using the SqlServer2008 data provider, BTW. |
|
|
|
|
Thanks for reporting this, we will have a look into a fix for you.
|
|
|
|
|
Thanks, Jeremy. I noticed that the same issue occurs with hyphens too. |
|
|
|
|
Quick update on this. Ive checked into this and the cause of this is due to the naming strategy we apply when extracting tables from the database which leads to a mismatch between what you have originally been allowed to enter and the subsequent name we infer when extracting. We cant make a change to the default strategy without introducing a breaking change so I am looking at what we can do from the designer end to resolve this up front. For now if you need to use an entity name with an underscore or hyphen you will need to use a custom design time naming strategy to resolve this or just ignore the suggested update. Let me know if you need info on the design time naming strategy approach.
|
|
|
|
|
Thanks for the update, Jeremy. This isn't a show stopper for us, but a workaround at some point would be nice. In the mean time, can you provide a list of characters that conflict with the current naming strategy? |
|
|
|
