Re: Antw: Re: revised gda-xml-query.dtd

[Vivien Malerba <malerba linuxave net>]

On mer, 26 jui 2000, you wrote:
> Hi Rodrigo,
> 
> you wrote:
> 
> > > > Then you can define a sequence as follows:
> > > >
> > > > <sequnce name="seq1">
> > > >    <property name="start" value="0"/>
> > > >    <property name="inc" value="1"/>
> > > > </sequence>
> > > 
> > > Ok, I forgot about it! I agree on this one, but we still have to define what
> > > information the client will get from objects like sequences, etc (in the SCHEMA
> > > stuff)
> > > 
> > but this <sequence> tag, wouldn't be better placed in the Database DTD
> > (for importing/exporting data) instead of the query DTD?
> 
> I introduced the 'sequence' element to be able to define a sequence, for example in Oracle:
> 
> <query>
>   <create>
>     <sequence name="seq1">
>      <property name="inc" value="1"/>
>      <property name="start" value="0"/>
>      <property name="maxvalue" value="1000"/>
>      <property name="cycle" value="yes"/>
>     </sequence> 
>   </create>
> </query>
> 
> would be rendered as 
> 
> create sequence seq1  increment by 2 start with 0 maxvalue 1000 cycle; 
> 
> If there is a surrounding Database DTD, that is included into the query DTD, then of course the sequence and surely some other elements should be
> moved to this DTD. Do you agree, Vivien?
> 

Yep. Rodrigo, could you explain what you want to include in the
database DTD, so we can make the query DTD work where the database DTD stops.
I do agree on this.

Regards,

Vivien