Changes between Version 16 and Version 17 of S3XRC/S3XML

Timestamp:

05/03/11 19:42:17 (13 years ago)

Author:

Dominic König

Comment:

--

S3XRC/S3XML

@@ -40 +40 @@
 ||'''Name'''||'''Type'''||'''Description'''||'''mandatory?'''||
 ||'''name'''||string||the name of the resource, usually the DB table name||''yes''||
-||'''uuid'''||string||a unique identifier for the record||''(yes)''*||
-||'''tuid'''||string||a temporary unique identifier for the record||''(yes)''*||
-
-(*) Records will be identified within the input file by their {{{uuid}}}, or, if no {{{uuid}}} is specified, by their {{{tuid}}}. While {{{uuid}}}s would be stored in the database and thus can be used to identify the record even in the database, {{{tuid}}}s will not be stored, but replaced by an internally generated UUID at import. Thus, {{{tuid}}}s cannot be used to update records in the database.
+||'''uuid'''||string||a unique identifier for the record||''no''*||
+||'''tuid'''||string||a temporary unique identifier for the record||''no''*||
+
+(*) Records will be identified within the input file by their {{{uuid}}}, or, if no {{{uuid}}} is specified, by their {{{tuid}}}.
+
+{{{uuid}}}s will be stored in the database together with the records. If {{{uuid}}} is present and matches an existing record in the database, then this record will be updated. If there's no match or no {{{uuid}}} specified in the {{{resource}}} element, then the importer will create a new record in the database (and automatically generate a {{{uuid}}} if required).
 
 ==== data ====