Atul,
Im looking at dbpsml-schema.xml...
<table name="JETSPEED_USER_PROFILE" idMethod="idbroker" >
<column name="PSML_ID" required="true" primaryKey="true"
autoIncrement="true" type="INTEGER"/>
<column name="USER_NAME" required="true" size="32" type="VARCHAR"/>
<column name="MEDIA_TYPE" size="99" type="VARCHAR"/>
<column name="LANGUAGE" size="2" type="VARCHAR"/>
<column name="COUNTRY" size="2" type="VARCHAR"/>
<column name="PAGE" size="99" type="VARCHAR"/>
<column name="PROFILE" required="true" type="LONGVARBINARY"/>
<unique name="JETSPEED_USER_PROFILE_UNIQUE">
<unique-column name="USER_NAME" />
<unique-column name="MEDIA_TYPE" />
<unique-column name="LANGUAGE" />
<unique-column name="COUNTRY" />
<unique-column name="PAGE" />
</unique>
<index name="JETSPEED_USER_PROFILE_INDEX">
<index-column name="USER_NAME" />
<index-column name="MEDIA_TYPE" />
<index-column name="LANGUAGE" />
<index-column name="COUNTRY" />
<index-column name="PAGE" />
</index>
</table>
Why do you need both:
<unique name="JETSPEED_USER_PROFILE_UNIQUE"> ...
and
<index name="JETSPEED_USER_PROFILE_INDEX">
i believe if you just have:
<unique name="JETSPEED_USER_PROFILE_UNIQUE">
its good enough, the unique index is created.
David
> I also found one problem with the generated SQL from Torque
> for Oracle.
> Since, the schema defines Index and Unique constraint on same set of
> columns. What Oracle does is, it automatically creates
> indexes on columns
> with unique constraint and specifying another unique
> constraints on the
> same set of columns, causes it to crib that the constraint on
> those columns
> exists. I tried to look into SQL specs for Index and Unique
> constraints,
> but couldn't find any semantics on unique constraint should
> be implemented
> in relational databases. If its a generic feature of all the
> relational
> databases to automatically generate indexes on columns with unique
> constraints, we can slightly modify the schema to get rid of
> specific index
> on same set of columns.
>
> > |-----src (the generated SQL for hypersonic,
> the default db -
> >which will also exist in om)
> > |-----templates
> > |
> > build.properties
> > build.xml
> >
> >While we are doing this, we could also drop all the scripts in
> >src/sql/external and add the turbine-schema.xml for turbine)
> >In fact we could combine the two xml files.
>
> Yes..sounds perfect.
>
> Thanks for handling all that, David.
>
> -Atul
>
> >What do you think?
> >
> >
> > > -----Original Message-----
> > > From: David Sean Taylor [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, October 11, 2001 9:12 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: 1.3a2 release
> > >
> > >
> > > > >3. Test and commit db-psml impl. from Atul, fix bug in
> > > > profiler for db-psml
> > > >
> > > > Also, depending upon the database, how can we generate Peer
> > > > classes for
> > > > Db-Psml in the build system..? We need to work on that
> > > aspect as well.
> > > >
> > >
> > > Interesting, thats something I didn't know about Torque.
> > > So the peer classes are actually different per database backend?
> > > I don't think that I like that.
> > >
> > >
> > > > >4. Update Configure How-to Guide
> > > >
> > > > Is that Update for db-psml How-to Guide as well?
> > > >
> > >
> > > Yes, I will add that to the docs todo list :-)
> > >
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> [EMAIL PROTECTED]
> > >
> > >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
