That is correct. The JDBC task doesn't change the names. But if you create the
classes (om) it creates the column names with uppercase letters and than there
is the problem because you cannot make any queries. Here is an example:
Generated XML file (correct):
table name=address
The column names in the class files should be generated in the same case as
they appear in the schema file. If this is not the case, this is a bug.
This is Torque 3.2 and you did not change anything there, I assume ? If
yes, would you mind to submit a bug report to Jira ?
Thomas
Thoralf
Okay, I'll submit a bug report.
-Ursprüngliche Nachricht-
Von: Thomas Fischer [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 17. Juli 2006 10:04
An: Apache Torque Users List
Betreff: AW: Sybase case insensitive column names
The column names in the class files should be generated
Hi,
IdBroker is no good for that. It uses an extra table and no sequences. In
native, Torque uses fixed names for the sequences it uses. See the
create-db sql for the names. Maybe you can rename your existing sequence to
fit that name ?
In the postgesql howto, there is also a paragraph about
Ok thanks,
so toruqe isn't really the right solution for a pre existing app.
I basically was trying to build some tools for a web app that used our
own set of persistence objects etc.
We made it well before there was anything decent out there.
Figured if torque can do it for me for this
Just a couple of quick comments. According to a quick read
of the SQL 99 standard, column names are supposed to be case
insensitive unless they are delimited. Sybase is doing
non-standard things here (or my interpretation could be
wrong 8) )
Also, changing the way Torque has generated
