Hi,
I've created that patch. The code in the ant task was all I could think of...
A check for database fields would be quite nice actually, when working on several machines, I sometimes forget to modify a table. That could be done by doing a find on every perstisted class (load will throw an error when it's not foud), and checking the exceptions
Another thing that's missing is checking the named sql queries (getNamedSQLQueries) Because of all dialects, the queries have to be executed. Maybe an EXPLAIN <SQL> would do, or a TX <SQL> rollback But it doesn't feel right..
Emmanuel Bernard wrote:
Actually the ant task wrapping is done and just call for a session factory build. Do you think it's enough?
Christian Bauer wrote:
On Jun 28, 2004, at 6:27 PM, Emmanuel Bernard wrote:
I would be ready to apply the YAGNI principle and not provide such param (yet).
What do you guys think?
I think it should be configurable. I've heard one or two requests for a "mapping validation tool" that you could run independently from Hibernate. It might be possible that we isolate such functionality, or at least, wrap it in an Ant task or something.
-------------------------------------------------------
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
