Q: What is the release schedule?
A: There is no fixed schedule. New public releases are made available each 4 to 8 weeks.
Q: Hi all! [
mehmet.sariyar@rizit.at @ 04.01.09:15:55:43 wrote]
Although tried any modifications described in the "how-to's", I wasn't already able to build up an inheritance using concept of setting superclasses primary-key as primary-and-foreign-key of the subclass. Everything is well functioning, the primitive fields of the superclass are been loaded together with the loaded subclass. BUT reference-descriptors and collection-descriptiors described in the super-class will be ignored, not give damn about them!
Here a look-like :
<class-descriptor class="A" table="A">
<field-descriptor id="0" name="pk_aid" column="PK_AID" jdbc-type="INTEGER" primarykey="true"
autoincrement="true"/>
<field-descriptor id="1" name="fk_broadid" column="FK_BroadID?" jdbc-type="INTEGER"/>
<field-descriptor id="2" name="fk_userid" column="FK_UserID?" jdbc-type="INTEGER"/>
<field-descriptor id="3" name="name" column="Name" jdbc-type="VARCHAR"/>
<field-descriptor id="4" name="unittyp" column="UnitTyp?" jdbc-type="CHAR"/>
<!-- begin:references -->
<reference-descriptor name="broad" class-ref="Broad"
auto-retrieve="true" auto-update="false" auto-delete="false">
<foreignkey field-ref="fk_broadid"/>
</reference-descriptor>
<reference-descriptor name="user" class-ref="User"
auto-retrieve="true" auto-update="false" auto-delete="false">
<foreignkey field-ref="fk_userid"/>
</reference-descriptor>
<!-- end:references -->
<!-- begin:collections -->
<collection-descriptor name="allCasts" element-class-ref="Cast"
auto-retrieve="true" auto-update="true" auto-delete="true"
orderby="pk_castid" sort="ASC">
<inverse-foreignkey field-ref="fk_aid"/>
</collection-descriptor>
<collection-descriptor name="allHistories" element-class-ref="History"
auto-retrieve="true" auto-update="true" auto-delete="true"
orderby="pk_historyid" sort="ASC">
<inverse-foreignkey field-ref="fk_aid"/>
</collection-descriptor>
<!-- end:collections -->
</class-descriptor>
<class-descriptor class="B" table="B">
<field-descriptor id="0" name="fk_aid" <!-- in RDBMS it is a primary-key and a foreign-key-reference in one -->
column="FK_AID" jdbc-type="INTEGER" primarykey="true"/>
<field-descriptor id="1" name="fk_clientid" column="FK_ClientID?" jdbc-type="INTEGER"/>
<!-- begin:references -->
<reference-descriptor name="super" class-ref="A"
auto-retrieve="true" auto-update="true" auto-delete="true">
<foreignkey field-ref="fk_aid"/>
</reference-descriptor>
<reference-descriptor name="client" class-ref="Client"
auto-retrieve="true" auto-update="true" auto-delete="true">
<foreignkey field-ref="fk_clientid"/>
</reference-descriptor>
<!-- end:references -->
</class-descriptor>
Does anyone have any experience with CONCEPT#3 of Inheritance O/R-Mapping ?