On Apr 15, 8:15 pm, Martin Buchleitner <[email protected]> wrote: > The problems i see is that the statement looks like > select count(*) from "my_table" where "field" = :somevalue > > This sql throws an exception because of the " characters. They shouldn't be a problem problem, as far as I can see, since the quotes are allowed by Oracle. They only prevent it from upper casing the identifiers and thus making it seems as if it is case sensitive (i.e. Oracle is always case sensitive, but if you leave off the quotes, the identifier is automatically upper cased).
But dblinq should use the right casing when generating the dbml-file, the code annotations, and when generating the sql, so how did you end up with a sql using the wrong casing? Is the casing correct in the code annotations and the dbml file? > i have overriden the Start and End Quote stuff. > Now the sqls work like a charm ... no problems at the moment. Next > week i gonna test the insert statements. If you removed the quotes then you might end up using the wrong table (e.g. both tables called "my_table" and "MY_TABLE" can exist in Oracle at the same time). > I am using System.Data.OracleClient.dll for .net 2.x ... Are the sqls > working only with Oracle.DataAccess.dll ? No, both the Oracle and the Microsoft provider should work. > Do you need some help at converting the unit tests? I'm not converting the unit tests as such. I looking at generating the sqls for the different vendors to make sure they are equivalent and remains so. But currently it is just an experiment. So not right now, but thanks. -- Anders -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
