hibernate-devel

[Hibernate] Mapping DTD changes

[Gavin K. <ga...@ap...>]

I've made some "improvements" to the mapping dtd.

* used enumerated attribute types everywhere
* the above required changing "save/update" cascade style to "save-update"
* introduced <key-many-to-one> and <key-property> elements for mapping
properties + associations that are part of a primary key
* replaced the use of <property> inside <composite-id> declarations with
<key-property>
* added <composite-index> and <index-many-to-many> elements, allowing a Map
with an association as part of its key.
* removed all the deprecated length attributes on foreign key elements like
<many-to-one>

Old mappings continue to work, they just don't conform to the new DTD. I
will try to provide support for both DTD versions for the near future.

(1) Does anyone know the best naming convention for new DTD versions?

Would this:

hibernate-mapping-1.1.dtd

be okay?

(2) Does anyone have any criticism of the new DTD changes? In particular,
better names for the new elements.

(3) Is there anything else anyone would like to see changed? Now would be a
good time to change/fix anything people find inelegant.

Re: [Hibernate] Mapping DTD changes

[Chris W. <cwi...@op...>]

On Mon, 2002-10-07 at 06:47, Gavin King wrote:
> I've made some "improvements" to the mapping dtd.
> ...
> * replaced the use of <property> inside <composite-id> declarations with
> <key-property>

For implementing a generated field as part of a composite ID, how would
I specify in the <composite-id> element which field is the generated
one? I hope to have this coded up soon, for all three people in the
world who need it :-)

Thanks,

Chris

-- 
Chris Winters (cwi...@op...)
Java Developer

Re: [Hibernate] Mapping DTD changes

[Gavin K. <ga...@ap...>]

Urrgghhh........you just *have* to have this do you?

;) j/k

ummmm.

Do you realize you can do stuff like:

IdentifierGenerator idgen = new HiLoGenerator();
id = idgen.generate( (SessionImplementor) session);

Its actually a bit of a hassle to support generation of *part* of a
composite identifier......


----- Original Message -----
From: "Chris Winters" <cwi...@op...>
To: "Gavin King" <ga...@ap...>
Cc: "hibernate list" <hib...@li...>
Sent: Tuesday, October 08, 2002 12:25 AM
Subject: Re: [Hibernate] Mapping DTD changes


> On Mon, 2002-10-07 at 06:47, Gavin King wrote:
> > I've made some "improvements" to the mapping dtd.
> > ...
> > * replaced the use of <property> inside <composite-id> declarations with
> > <key-property>
>
> For implementing a generated field as part of a composite ID, how would
> I specify in the <composite-id> element which field is the generated
> one? I hope to have this coded up soon, for all three people in the
> world who need it :-)
>
> Thanks,
>
> Chris
>
> --
> Chris Winters (cwi...@op...)
> Java Developer
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Re: [Hibernate] Mapping DTD changes

[Chris W. <cwi...@op...>]

On Mon, 2002-10-07 at 11:40, Gavin King wrote:
> Do you realize you can do stuff like:
> 
> IdentifierGenerator idgen = new HiLoGenerator();
> id = idgen.generate( (SessionImplementor) session);
> 
> Its actually a bit of a hassle to support generation of *part* of a
> composite identifier......

I know, I know. But this is the problem with retrofitting -- I really
cannot change the existing schema. (Picture trying to get the sun to
rise in the West and set in the East...)

I'm pretty sure I've got the logic and code nailed down ok, I just need
to be able to identify which of the fields is generated.

Chris

-- 
Chris Winters (cwi...@op...)
Java Developer