[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ozone IDs through XML import/export
On Sun, 11 Mar 2001, Reason wrote:
> Am I correct in assuming the presence of object IDs in the Ozone export XML
> means that internal database IDs [i.e.
> ozoneobject.container().id().getValue()] will remain invarient through a
> cycle of exporting the entire database as XML and then importing it to a
> fresh and empty database?
Yes, the remain invariant. The object ID _is_ the identity of an object.
> I'm in the process of hacking together a restricted object description model
> for some later development that requires all objects to have a unique ID and
> reference one another via this ID rather than containment or Java
> references. (Don't ask: it makes sense in context :). Using the internal
> Ozone methodology of ID assignment is the easiest method of unique ID
> assignment by far, but invarience across imports/exports becomes
> important...
The only problem I see is that ozone object ID are not meant to be explicitly
used by client code. There is no 'official' API to access them. So, there is a
very very small chance that this API will change in future versions.
Falko
--
______________________________________________________________________
Falko Braeutigam mailto:falko@smb-tec.com
SMB GmbH http://www.smb-tec.com