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)
> > I suggest that named query validation be done by the
> > Dialect implementation, rather than by checking against a live DB.
>
> Why the dialect? It doesn't know about the schema, does it?
Ok, I guess I wasn't being particularly precise when I suggested the Dialect. The
complete validat
See my comments below. (Please remember that I'm the FNG around here so my
comments might be dumb ;->).
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Aaron Knauf
> Sent: Tuesday, June 29, 2004 6:24 PM
> Subject: RE
u have done so with competence.
That was my $0.02 worth.
Cheers
ADK
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Max
> Rydahl Andersen
> Sent: Wednesday, June 30, 2004 6:08 AM
> To: Joris Verschoor
> Cc: [EMAIL PROTECTED
Hello guys,
What we need is two things:
1. check the , , mapping etc. against the database
2. check if the namedQueries are valid
This stuff should be:
- as correct as possible/necessary
- as fast as possible/necessary
...but most important as usable and maintainable as possible!
Using some
