-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 03 April 2003 12:03, Manske, Michael wrote: > Hi all, > > seems as nobody cares that problem :-) > Ok, i will explain why i think that is really important: [...] > Conclusion: Torque's O/R mapping through peers and the xml-schema > presupposes non-changing clolumn name in database. Torque does not provide > "loose coupling" between java objects and database.
i might be mistaken, but i suppose javaName was more or less meant as a "cosmetic" thing to deal with capitalization? (at least, that's how i use it) in my opinion, using different names for attributes in your application and in your database is a really Bad Idea, because it does nothing more than confuse. why would you need this? rick - -- |- | peter riegersperger <[EMAIL PROTECTED]> |- | subnet | platform for media art and experimental technologies |- | http://www.subnet.at/ |- | muehlbacherhofweg 5 // 5020 salzburg // austria |- | fon/fax +43/662/842 897 |- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+jAkdIMP39JYOy9IRAgLzAKChjjiCxAFEVXxvaIj1vYhzHzwXtACffQFM YaighC70nS5Aa16YXSpFKPI= =QO4m -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
