Michael Gloegl wrote:
- Let people pass in the resulting class, e.g. createSqlQuery("...", {"user", "username"}, {User.class, String.class}). Then pass the classname to heuristicType. This sucks, because heuristcType can not guess fitting UserTypes and does not work at all for ParameterizedTypes.
Yes, this does not work well.
- Let people pass in a mix of Types and Classes by changing the API to accept an Object array, e.g. createSqlQuery("...", {"user", "username"}, {User.class, Hibernate.STRING}). This is also not very nice because it reduces API typesafty and feels generally a bit dirty.
This would be ok, I think.
- Change the API to accept a Type[] instead of a Class[], e.g. createSqlQuery("...", {"user", "username"}, {Hibernate.entity(User.class), Hibernate.STRING}). Also sucks because it breaks existing code.
Naw, that is not really the semantics of EntityType. You're muddying the concept of "Type".
-- Gavin King +61 410 534 454 +1 404 822 8349 callto://gavinking
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
