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
|
Hi, I just downloaded the latest build and it solved the problem of forgetting to put the correct column name into the attribute when converting property names to proper case. It did not however solve the problem of quoted column names getting translated incorrectly. In oracle to ensure that columns are properly cased for us we sometimes quote the column names so, CREATE TABLE "Foo" ("Bar" VARCHAR2(10)); This should result in a table attribute of "\"Foo\"" for the name(NOT "FOO") and a column name attribute of "\"Bar\"" (NOT "BAR") Thanks |
|
|
|
|
Thanks for reporting this issue. Unfortunately Oracle doesn't make it tremendously easy for us to determine whether a name is quoted (case-preserved) or not, so this may be a tricky one to fix. (We don't want to quote the table or column name if it's non-case-preserved.) A workaround for this is to enter the quotes manually into the Properties window, e.g. change Foo to "Foo". This will result in the table or column name being quoted in the generated code (with appropriate escaping, i.e. [Column("\"Foo\"") in C# or <Column("""Foo""")> in Visual Basic). Is this viable for you, or do you have a very large number of quoted column names? You might also want to look at the LightSpeedContext.QuoteIdentifiers property, though this is a bit of a blunt instrument and may not work if you have a mix of quoted and non-quoted names. I will log a bug for this and investigate further; thanks again for reporting it. |
|
|
|
