On Thu, 26 Oct 2000, Fedor Karpelevitch wrote:
> Hi!
>
> This and similar issues have been already addressed in newtorque by adding
> javaName attribute to table and column elements.
> You may use it to specify name to be used to reference the table/column in
> the Java code. It will preserve the case you specify and it is also a good
> idea to use this attribute to handle the differences between SQL and Java
> naming conventions, such as:
>
> VISITOR.VISITOR_ID makes a lot of sense in SQL, however in Java you are much
> better having visitor.getId() instead of visitor.getVisitorId(); This can be
> easily accomplished in newtorque as foloows:
>
> <column name="VISITOR_ID" javaName="Id" ..../>
>
> also newtorque has some other advantages over torque
> so, as you could understand, I encourage you to look at newtorque.
>
> Fedor.
>
> PS. BTW, what do you guys think about 'officially' redirecting all feature
> work from torque to newtorque?
I definitely plan to use new torque. I was going to try to
merge the two of them. What's the SQL generation like
in new torque? I just use torque a lot for my own stuff,
so I'm used to it. I am definitely for merging the two, getting
rid of most of the old torque stuff and using most of the
new torque goodies. I'll be looking at all the torque stuff,
I'll move all the new torque goodies into the torque while
I'm trying to get it to work in the TDK if that's all right
with everyone.
jvz.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
