Ara Abrahamian wrote:
And this will take into account cascade=all|delete too?
My bad, when I wrote "orphan delete", I meant to say "casade delete". It
would not work for orphan delete.
--
Gavin King
JBoss Group
+61 410534454
http://hibernate.org
Max Rydahl Andersen wrote:
> ok - so instead of deleting one at the time, we batch delete, but still
call all the lifecycle stuff ?
> (but isn't the users just going to ask for a quick batch delete instead
then (to avoid the possible expensive delete ? ;)
I'm sure they will /ask/.
--
Gavin
Giovanni Formenti wrote:
Someone tried to do jaas authentication via Hibernate and extend the
SimplePrincipal to store more information about logged user?!
I'm trying to integrate this in JBoss 3.2.3...
I read http://www.hibernate.org/139.html but few information are available
there.
Someone have e
Use the Hibernate forum for user questions.
> Hi,
>
> I am trying to create a query based on the values of a map containing
> composite-elements. I have a Map property called propertiesMapped. The
> elements withing this map are mapped as composite-elements. I want to
> join only based on a pro
Hi,
I am trying to create a query based on
the values of a map containing composite-elements. I have a Map property
called propertiesMapped. The elements withing this map are mapped as
composite-elements. I want to join only based on a property of the
composite-element, in my example t
> > It will just be built underneath existing functionality like
> > delete(query) and orphan delete. It will support all
> > Hibernate semantics. So this:
> >
> > session.delete("from Foo foo where foo.name like 'foo'")
> >
> > will cause two queries:
> >
> > SELECT ... FROM FOO WHERE NAME LIKE 'f
Someone tried to do jaas authentication via Hibernate and extend the
SimplePrincipal to store more information about logged user?!
I'm trying to integrate this in JBoss 3.2.3...
I read http://www.hibernate.org/139.html but few information are available
there.
Someone have examples of this or can g
