Changes between Version 11 and Version 12 of S3XRC/S3XML


Ignore:
Timestamp:
05/03/11 19:28:26 (11 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • S3XRC/S3XML

    v11 v12  
    4040||'''Name'''||'''Type'''||'''Description'''||'''mandatory?'''||
    4141||'''name'''||string||the name of the resource, usually the DB table name||''yes''||
    42 ||'''uuid'''||string||a unique identifier for the record||''(yes)''**||
    43 ||'''tuid'''||string||a temporary unique identifier for the record||''(yes)''**||
    44 
    45 (**) 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.
     42||'''uuid'''||string||a unique identifier for the record||''(yes)''*||
     43||'''tuid'''||string||a temporary unique identifier for the record||''(yes)''*||
     44
     45(*) 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.
    4646
    4747==== data ====