I was trying to write it as UserType.
But I couldn't obtain the same functionality that I have with a
hibernate component, because I find no way to implement an UserType that
some of his properties be part of a manytoone or onetomany relation.
Pablo
Max Rydahl Andersen wrote:
On Fri, 10 Mar
On Fri, 10 Mar 2006 20:44:14 +0100, Pablo Nussembaum
<[EMAIL PROTECTED]> wrote:
I know that, but this a common glitch that some hibernate users
complains.
I think that this behavior is more natural to final user as its follow
the minimal surprise concept. Why if the component has all nulls
p
I know that, but this a common glitch that some hibernate users complains.
I think that this behavior is more natural to final user as its follow
the minimal surprise concept. Why if the component has all nulls
properties and in the db all the fields were null, hibernate generates
and update?
Pa
you should probably use a UserType to code such application semantic.
Pablo Nussembaum wrote:
Hi,
I made a simple modification in the ComponentType class to consider
null component equals to a components with all his properties nulls.
I do this to address 2 problems I have:
1. For sim
Hi,
I made a simple modification in the ComponentType class to consider
null component equals to a components with all his properties nulls.
I do this to address 2 problems I have:
1. For simplicity in all entities, when a components is null the
getters builds a new instance and th
