Marcelo Vanzin <[EMAIL PROTECTED]> writes:
> I was tracking some errors I got when running the turbine-oracle.sql
> script, and found that in turbine-schema.xml you are trying to create
> indexes for columns that are already primary keys, like this:
>
> <column name="ROLE_ID" required="true" index="true"
> primaryKey="true" type="INTEGER"/>
> <column name="PERMISSION_ID" required="true" index="true"
> primaryKey="true" type="INTEGER"/>
>
> <index name="ROLE_PERMISSION_INDEX">
> <index-column name="ROLE_ID"/>
> <index-column name="PERMISSION_ID"/>
> </index>
>
> This generates an error in Oracle, although everything installs OK (the
> command is just ignored, and the index is created along with the primary
> key). Is this redundancy needed (for some other database)?
A redundant index is ignored by MySQL, but I would prefer to drop the
redundancy if it is not needed by other databases.
Daniel
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
