From: max <ma...@ac...> - 2003-01-02 07:11:06
|
Could you give an hbm.xml and query example that gives that error ? (it would be nice to have some test scenario :) (especially, since it would be nice to know what one could do to avoid such a thing....- it would also be a problem on db2 since it also has some "weird" low limitations) /max >Yick. The biggest design problem with Hibernate at present is >the fact that we have no single class responsible for rendering >SQL. (As I have mentioned before, Hibernate models SQL >statements using StringBuffer...) So little things like this >that should be *very* easy turn out to be way more tricky >than you expect. However there are a couple of methods that >are responsible for dealing with SQL quoted identifiers so >you may be able to hook in there. > >We *do* need to fix this problem of StringBuffer being used >everywhere. > > > >>-----Original Message----- >>From: Mark Woon [mailto:mor...@SM...] >>Sent: Wednesday, 1 January 2003 10:33 AM >>To: Hibernate Mailing List >>Subject: [Hibernate] Length of Hibernate-generated aliases in SQL >> >> >> >>Does Hibernate do any checking on the length of the aliases >>it generates >>when it creates it's SQL queries? I'm getting "identifier is >>too long" >>errors against Oracle 9.2 at the moment because Hibernate >>tacks on some >>extra text to some column names. >> >>If not, would it be terribly difficult to add this >>functionality? Which >>classes should I be looking at to figure this out? >> >>Thanks, >>-Mark >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>hibernate-devel mailing list hib...@li... >>https://lists.sourceforge.net/lists/listinfo/hibernate-devel >> >> >> |