Gary,
Not sure about the restriction on the ids being in order. Seems that I, like
you, have experimented with that and found that the order didn't SEEM to
have an effect. I emphasize 'seem' because I didn't notice any failure for
the small test that I ran. I also found that the numbers did not have to be
contigous. That is, there could be gaps without ill effects. (This could
occur if, after numbering, attributes were removed due to refactoring) The
caveat to this last is that it will NOT succeed if any of the higher
numbered attributes is referred to by a reference-descriptor. (Unless I did
it wrong).
As an example, let's say that I have a class with 7 attributes. But because
of gaps, they are numbered through 9, and I have:
<field-descriptor id="9" ...........>
<reference-descriptor name="blahblah" .......>
<foreignkey field-id-ref="9"/>
This will cause a ArrayIndixOutofBounds exception when attempting to
reference field-id-ref=9.
But other than that, ordering of the ids did not seem to matter.
Dave Derry
----- Original Message -----
From: "Gary A. Bartlett" <[EMAIL PROTECTED]>
> The repository documentation includes the following note about the id
> attribute of the field-descriptor element:
>
> "The id attribute must contain a unique number identifying the
> decriptor. The numbers for the attributes of a class must correspond to
the
> order of columns in the mapped table."
>
> This second part about matching the order of the columns in the mapped
table
> seems a bit restrictive to me. I wonder is this something that is
required
> only for certain OJB queries? As a test I modified the id attributes in a
> test table I am working on, such that the order did not match, and
> everything still worked correctly.
>
> The reason this is important to me is that I plan to create the repository
> file automatically and cannot necessarily ensure that I assign id values
> that correspond to the order of the columns in the table.
>
> Any information is appreciated.
>
> Gary Bartlett
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
