|
From: Steve E. <ste...@jb...> - 2006-05-10 16:53:12
|
yep -----Original Message----- From: Emmanuel Bernard=20 Sent: Wednesday, May 10, 2006 10:41 AM To: Steve Ebersole; 'emm...@hi...'; 'hib...@li...' Subject: Re: [Hibernate] Issue with pluggable functions Yes add back the old method signature We will remove it at a latter release Mark it as deprecated -----Original Message----- From: Steve Ebersole <ste...@jb...> To: Emmanuel Bernard <emm...@hi...>; Hibernate development <hib...@li...> Sent: Wed May 10 09:49:46 2006 Subject: RE: [Hibernate] Issue with pluggable functions Sorry, my fault. I forgot that we added that call to your stuff. =20 We really need this changed though to properly allow for (1) classic aggregation registration and (2) better user function registration.=20 =20 The other thing I could do is add back the old signature which would only be for your use, and which would not account for user-registered functions (planned feature). That work? =20 ________________________________ From: hib...@li... [mailto:hib...@li...] On Behalf Of Emmanuel Bernard Sent: Wednesday, May 10, 2006 9:05 AM To: Hibernate development Subject: [Hibernate] Issue with pluggable functions =20 public static String renderWhereStringTemplate(String sqlWhereString, Dialect dialect, SQLFunctionRegistry functionRegistry)=20 Breaks binary compatibility with Hibernate Annotations 3.2.0.CR1 |