It should be TURBINE_ROLE
that can be fixed in the turbine-schema.xml file which is then used
to generate all the *.sql files
mike
On Mon, Dec 04, 2000 at 09:05:13PM +0100, Andre Schild wrote:
> In the sybase sql script there are still two problems:
>
> 1. In the following code, the alter-statement of the constraints, must be wrapped in
>BEGIN ... END statements, just as in the drop table sequences.
>
> IF EXISTS (SELECT 1 FROM sysobjects WHERE type ='RI' AND
>name='TURBINE_ROLE_PERMISSION_FK_1')
> ALTER TABLE TURBINE_ROLE_PERMISSION DROP CONSTRAINT TURBINE_ROLE_PERMISSION_FK_1
> GO
>
>
> 2. On line 172 we see the following text:
>
> ALTER TABLE TURBINE_USER_GROUP_ROLE
> ADD CONSTRAINT TURBINE_USER_GROUP_ROLE_FK_3 FOREIGN KEY (ROLE_ID)
> REFERENCES TURBINE_USER_ROLE (ROLE_ID)
> GO
>
> It references the TURBINE_USER_ROLE table.... but this one just doesn't exist...
> The same reference exists in: turbine-db2.sql , turbine-mysql.sql turbine-oracle.sql
>and turbine-postgres.sql !!!!!!
>
>
> Andr�.
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
