Hi, Aaron wrote:
[snip] Those cases where Hibernate generates SQL that is not compatible with a specific database should be treated as bugs in Hibernate. (i.e. The Dialect implementation is incorrect.) What I would like to see is one of two types of exception thrown during HQL compilation: 1) An exception to indicate that your HQL syntax is incorrect, (or does not match your class model,) regardless of dialect. 2) An exception that indicates that your HQL, while sytactically correct and matching your class model, cannot be compiled with the given Dialect, because the Dialect does not support some feature that you have used. [snip] Tool support is great in respect to 2). There is also an issue of documentation and education here. As part of developing this 'hbmlint' tool or a separate effort I would really like to see a table that actually lists the features of Hibernate HQL(and potentially the implicit CRUD that Hibernate generates) that are not supported by different Dialects. This table is needed anyway in order to formalize query checking as proposed by Aaron above. This would increase the level of preparedness in 2 scenarios: 1) when developing a new application for a particular DB I would know up-front what to avoid instead of later refactoring my "broken" queries 2) when porting an existing Hibernate application to a new DB I would be able to estimate the time necessary even without running the tool. Does this make any sense? Oleg Proudnikov [EMAIL PROTECTED] cell: (416) 418-5588 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
