RE: Re: AW: [Objectbridge-jdo-dev] jdo extension
Brought to you by:
thma
From: <tr...@th...> - 2002-05-24 20:47:35
|
>But I think its better to use the same syntax as in the (1.0) > repository.dtd: Fine by me as long as everyone is in agreement. > What about primary keys and foreign keys for references and collections? Collections, already handled in the spec, excerpt below: 18.4.1 ELEMENT collection This element specifies the element type of collection typed fields. The default is Collection typed fields are persistent, and the element type is Object. The element-type attribute specifies the type of the elements. The embedded-element attribute specifies whether the values of the elements should be stored if possible as part of the instance instead of as their own instances in the datastore. It defaults to "false" for persistence-capable types and interface types; and "true" for other types. Java Data Objects1.0 18.4.2 ELEMENT map This element specifies the treatment of keys and values of map typed fields. The default is map typed fields are persistent, and the key and value types are Object. The key-type and value-type attributes specify the types of the key and value, respectively. The embedded- key and embedded-value attributes specify whether the key and value should be stored if possible as part of the instance instead of as their own instances in the datastore. They default to "false" for persistence-capable types and interface types; and "true" for other types. 18.4.3 ELEMENT array This element specifies the element type of array typed fields. The default is array typed fields are persistent, according to the rules above. The embedded-element attribute specifies whether the values of the elements should be stored if possible as part of the instance instead of as their own instances in the datastore. It defaults to "false" for persistence- capable element types and interface types; and "true" for other types. > Any ideas about default naming conventions? Do you mean default name mapping from java field to table column? If so, I would say identical to the java field name. ex: quantity -> quantity productGroup -> productGroup Same for class names to tables. travis |