Carl Ludewig wrote:
> > This might be a problem. We standardized on having all uppercase column
> > names because some databases need to have that. Therefore, for portability
> > reasons, I suggest that you do the same with your code (even if today you
> > won't be using your stuff on other databases).
>
> It's not entirely under my control. We have a DBA here at AudioBase who
> sets up the naming conventions for the db. In any case, if the XML is all uppercase,
> it doesn't matter anyway and the toUpperCase is unnecessary. If it's an issue,
> I'd happy to add a feature to Torque that's allows one to turn all uppercase mode
> on/off with a default of uppercase.
A switch would be reasonable. I'm also using mixed case table/column
names in my
system and Torque was happily breaking them. I know about another
workaround,
which is using java_name (or was it javaname) in your xml schema, but
I'd prefer
a switch to just leave the names alone.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
