Re: How to combine two non-decomposed m:n mappings in one collection?

[Patrick Scheuerer]

Coup, Robert Muir wrote:

Hi,

Did you see my response to your other post? Please reply to the list.
No I didn't, sorry! I somehow gave up on this post...

Idea #2:
How about:
<class-descriptor class="SupportItemI">
  <extent-class class-ref="Document"/>
  <extent-class class-ref="Download"/>
</class-descriptor>
<class-descriptor class="pal_model" table="t_pal_model">
  ... Field Descriptors ...
  <collection descriptor name="collectionOfSupportItemIs"
	element-class-ref="SupportItemI"
	indirection-table="t_pal_model_supportitems"
	>
	<fk-pointing-to-this-class column="model_id"/>
	<fk-pointing-to-element-class column="SupportItemID"/>
  </collection-descriptor>
</class-descriptor> 

<class-descriptor class="download" table="t_download">
  ... Field Descriptors ...
  <collection-descriptor name="models"
        element-class-ref="pal_model"
        indirection-table="t_download_pal_model"
        >
        <fk-pointing-to-this-class column="SupportItemID"/>
        <fk-pointing-to-element-class column="model_id"/>
  </collection-descriptor>
</class-descriptor>
You should be able to keep your object design the same and just modify
the tables a bit so there is one table for both relations... Still
non-decomposed :)
This sounds interesting. Just let me make sure I got it right:
I have to create a new table t_download_supportitemI which has a m:n mappings to 
t_download and and one to t_document (pretty much a replacement for t_pal_model) 
and t_pal_model has a 1:n mapping to t_pal_model_supportitemI... is that correct?

Thank you very much for your detailed examples!

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]