Re: [Gusdev-gusdev] GUS 3.0 schema changes

[Arnaud K. <ax...@sa...>]

Hi

A quick question. Do I need to specify the primary key or it is 
automatically generated by the plugin if it is missing ?

Soon I know the answer to this, I can generate XML for two controlled 
vocabulary tables: Mutagen and PhenotypeClass.
FYI the controlled vcabularies will be based on Flybase ones.

Arnaud

Angel Pizarro wrote:

>The  XML parsing is currently handled by the GUSRow module (formerly
>RelationalRow). As such, there are a few constraints on the creation of
>GUS XML objects, in addition to using the fully qualified object names.
>1) It relies on newlines to get valid input. YOU MUST put object
>declaration on a separate line that attribute declarations. For instance
>the following do not work:
>
><GUS::Model::RAD::Array><name> PancChip </name>
></GUS::Model::RAD::Array>
>
><GUS::Model::RAD::Array>
><name> PancChip </name> <version> 1.2</version>
></GUS::Model::RAD::Array>
>
>2) To force a submit while parsing a GUS XML doc, enter the characters
>"//" on a separate line. I am not sure this is valid XML, but I suspect it
>is due to backwards compatability issues with SGML.
>
>
>I am working in my spare time (of which there is not much) to switch to an
>actual XML parser, rather than use of regular expressions (as is now the
>case). At the same time, I will swith the XML syntax to match a more
>database centric scheme, by using the tag attributes as the table columns,
>instead of subelements:
>
><Object
>	att1 = 'val1'
>	att2 = 'val2'
>	...
>
>	<Child Object .../>
></Object>
>
>But this is not anywhere near finished (in fact just started) so for now
>we must live with the constaints as they stand.
>
>Angel
>
>  
>