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
|
When I create the model, the Column names are converted to pascal case eg. column CODE in the DB is represented by <property name='Code' column='`Code`'/> in the mapping XML. The problem is, our Oracle datebase is case-sensitive and I will not be able to change that. I can obviously get around this by editing the xml or the properties in the designer but it will add quite a lot of work. Is there a setting I've missed that will stop the names being translated? If not, are you able to add that feature in please? Thanks, Callum |
|
|
|
|
Hello Callum, You can turn off quoting in the mapping XML by setting Quote Identifiers to False at the model level. However because you have a database where the tables have been created with cased names, I believe you do need the quoting, but also need us to preserve the casing of the table names in the database. This has required an update to the software. If you check the Visual Studio Extensions Manager now you should find an update which does this (it sometimes takes a while for updates to appear in Extensions Manager so please be patient). You will need to re-drag tables from Server Explorer to recreate the entities with the correctly cased table names. Please let us know if it doesn't solve your problem. |
|
|
|
|
Hi Ivan, Thanks for that. I've tried it (just to confirm I got the right version, it's 1.0.345.15894) and it doesn't seem to have fixed the issue... I do have Quote Identifiers set to True but when I drag the tables over to the designer, the column names are still switching to Pascal case. I've also tried it with Quote Identifiers set to False but it doesn't make any difference. Thanks, Callum |
|
|
|
|
I'm a cabbage. I fixed the issue for table names but not for column names. Sorry about that. There should be a fix available through Extension Manager in 5-10 minutes. Apologies again for the ***-up! |
|
|
|
|
I can confirm that this is now updated and the update should be available in your Extension Manager. |
|
|
|
|
Ha ha, that's all right! All works perfectly now, thanks... Cheers, Callum |
|
|
|
