First of all, since picking up Hibernate on a project and using it for a
month or two (and having used a few other similar systems), and having
some occasions to hunt around in the source, I wanted to write just to say
that I was impressed by the clarity, concision, and overall good
experience
> hmmmdon't know if it would be great to hold a reference to an object
> in the exception...but maybe extend the message with information
> (textual representation of the object) would probably be ok
OK. So, add a toString() to the JDBCException's message. It's a good idea.
I want to m
I just did a swing client that uses hibernate, and although in my case I
was alright to make the database available to the client hosts, I'm sure
many can't. So it sounds like this will certainly be useful, but it has me
thinking: will this layer be added only because nobody trusts the
database
lability purposes.
>
> I guess this argument against doing it at the JDBC level also applies
> to doing it at the ORM level, since it still opens up the possibility of
> arbitrary queries.
>
>
> David Wood wrote:
>
> >I just did a swing client that uses hibernate, an
Outer join fetching has never been good to me. Hibernate always seemed to
ignore my OJ configuration settings and metadata, at least for where it
mattered for me (on collections). Eventually I discovered the correct
language in HQL queries to "force" it to happen: "from Parent as p left
join fe
