I don't think we are realistically going to be able to dream up portable aliases for everything. I can see an argument for doing it for a couple of very important cases like current date. Beyond that I wouldn't really like to go there. Note that you can't have both really ... as soon as you have too many aliases, they start to clobber the namespace of proprietary and user-defined functions.

Note also that the user can define portable aliases for themselves in the current parser, by specifying hibernate.query.substitutions.

Joshua Davis wrote:

David,

Excelent point. It looks like a design decision is required here (i.e.
portable aliases vs. proprietary pass-through).  Personally, I like the idea
of portable aliases for special features, as I'm not sure how I'm going to
plug Hibernate's dialect information into the parser.  It's probably not to
hard to do that though, if someone would be kind enough to point me at the
right part of the Hibernate API.  :)


Josh



------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to