You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Dan Cancro <DC...@bridgespan.com> on 2001/08/17 01:32:43 UTC
oracle-turbine.sql sequences?
I just downloaded Turbine for the first time today and am trying to get it
working with my Oracle 8i database. In step 7 of the Oracle 8i how-to page,
http://jakarta.apache.org/turbine/howto/oracle-howto.html, it says that
oracle-turbine.sql creates sequences for each table. I'm not seeing how it
does this.
Here are the contents of oracle-turbine.sql:
----------------------------------------------------------------------------
-
-- TURBINE_PERMISSION
----------------------------------------------------------------------------
-
drop table TURBINE_PERMISSION cascade constraints;
CREATE TABLE TURBINE_PERMISSION
(
PERMISSION_ID INT NOT NULL,
PERMISSION_NAME VARCHAR2 (99) NOT NULL,
OBJECTDATA LONG RAW,
UNIQUE (PERMISSION_NAME)
);
ALTER TABLE TURBINE_PERMISSION
ADD CONSTRAINT TURBINE_PERMISSION_PK
PRIMARY KEY (PERMISSION_ID);
----------------------------------------------------------------------------
-
-- TURBINE_ROLE
----------------------------------------------------------------------------
-
drop table TURBINE_ROLE cascade constraints;
CREATE TABLE TURBINE_ROLE
(
ROLE_ID INT NOT NULL,
ROLE_NAME VARCHAR2 (99) NOT NULL,
OBJECTDATA LONG RAW,
UNIQUE (ROLE_NAME)
);
ALTER TABLE TURBINE_ROLE
ADD CONSTRAINT TURBINE_ROLE_PK
PRIMARY KEY (ROLE_ID);
----------------------------------------------------------------------------
-
-- TURBINE_GROUP
----------------------------------------------------------------------------
-
drop table TURBINE_GROUP cascade constraints;
CREATE TABLE TURBINE_GROUP
(
GROUP_ID INT NOT NULL,
GROUP_NAME VARCHAR2 (99) NOT NULL,
OBJECTDATA LONG RAW,
UNIQUE (GROUP_NAME)
);
ALTER TABLE TURBINE_GROUP
ADD CONSTRAINT TURBINE_GROUP_PK
PRIMARY KEY (GROUP_ID);
----------------------------------------------------------------------------
-
-- TURBINE_ROLE_PERMISSION
----------------------------------------------------------------------------
-
drop table TURBINE_ROLE_PERMISSION cascade constraints;
CREATE TABLE TURBINE_ROLE_PERMISSION
(
ROLE_ID INT NOT NULL,
PERMISSION_ID INT NOT NULL
);
ALTER TABLE TURBINE_ROLE_PERMISSION
ADD CONSTRAINT TURBINE_ROLE_PERMISSION_PK
PRIMARY KEY (ROLE_ID,PERMISSION_ID);
ALTER TABLE TURBINE_ROLE_PERMISSION
ADD CONSTRAINT TURBINE_ROLE_PERMISSION_FK_1 FOREIGN KEY (ROLE_ID)
REFERENCES TURBINE_ROLE (ROLE_ID)
;
ALTER TABLE TURBINE_ROLE_PERMISSION
ADD CONSTRAINT TURBINE_ROLE_PERMISSION_FK_2 FOREIGN KEY (PERMISSION_ID)
REFERENCES TURBINE_PERMISSION (PERMISSION_ID)
;
----------------------------------------------------------------------------
-
-- TURBINE_USER
----------------------------------------------------------------------------
-
drop table TURBINE_USER cascade constraints;
CREATE TABLE TURBINE_USER
(
USER_ID INT NOT NULL,
LOGIN_NAME VARCHAR2 (32) NOT NULL,
PASSWORD_VALUE VARCHAR2 (32) NOT NULL,
FIRST_NAME VARCHAR2 (99) NOT NULL,
LAST_NAME VARCHAR2 (99) NOT NULL,
EMAIL VARCHAR2 (99),
CONFIRM_VALUE VARCHAR2 (99),
MODIFIED DATE,
CREATED DATE,
LAST_LOGIN DATE,
OBJECTDATA LONG RAW,
UNIQUE (LOGIN_NAME)
);
ALTER TABLE TURBINE_USER
ADD CONSTRAINT TURBINE_USER_PK
PRIMARY KEY (USER_ID);
----------------------------------------------------------------------------
-
-- TURBINE_USER_GROUP_ROLE
----------------------------------------------------------------------------
-
drop table TURBINE_USER_GROUP_ROLE cascade constraints;
CREATE TABLE TURBINE_USER_GROUP_ROLE
(
USER_ID INT NOT NULL,
GROUP_ID INT NOT NULL,
ROLE_ID INT NOT NULL
);
ALTER TABLE TURBINE_USER_GROUP_ROLE
ADD CONSTRAINT TURBINE_USER_GROUP_ROLE_PK
PRIMARY KEY (USER_ID,GROUP_ID,ROLE_ID);
ALTER TABLE TURBINE_USER_GROUP_ROLE
ADD CONSTRAINT TURBINE_USER_GROUP_ROLE_FK_1 FOREIGN KEY (USER_ID)
REFERENCES TURBINE_USER (USER_ID)
;
ALTER TABLE TURBINE_USER_GROUP_ROLE
ADD CONSTRAINT TURBINE_USER_GROUP_ROLE_FK_2 FOREIGN KEY (GROUP_ID)
REFERENCES TURBINE_GROUP (GROUP_ID)
;
ALTER TABLE TURBINE_USER_GROUP_ROLE
ADD CONSTRAINT TURBINE_USER_GROUP_ROLE_FK_3 FOREIGN KEY (ROLE_ID)
REFERENCES TURBINE_ROLE (ROLE_ID)
;
----------------------------------------------------------------------------
-
-- TURBINE_SCHEDULED_JOB
----------------------------------------------------------------------------
-
drop table TURBINE_SCHEDULED_JOB cascade constraints;
CREATE TABLE TURBINE_SCHEDULED_JOB
(
JOB_ID INT NOT NULL,
SECOND INT default -1 NOT NULL,
MINUTE INT default -1 NOT NULL,
HOUR INT default -1 NOT NULL,
WEEK_DAY INT default -1 NOT NULL,
DAY_OF_MONTH INT default -1 NOT NULL,
TASK VARCHAR2 (99) NOT NULL,
EMAIL VARCHAR2 (99),
PROPERTY LONG RAW
);
ALTER TABLE TURBINE_SCHEDULED_JOB
ADD CONSTRAINT TURBINE_SCHEDULED_JOB_PK
PRIMARY KEY (JOB_ID);
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: oracle-turbine.sql sequences?
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Dan Cancro <DC...@bridgespan.com> writes:
> I just downloaded Turbine for the first time today and am trying to get it
> working with my Oracle 8i database. In step 7 of the Oracle 8i how-to page,
> http://jakarta.apache.org/turbine/howto/oracle-howto.html, it says that
> oracle-turbine.sql creates sequences for each table. I'm not seeing how it
> does this.
You need to set idMethod="native" (or idMethod="sequence" in the
stable branch).
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: oracle-turbine.sql sequences?
Posted by Jon Stevens <jo...@latchkey.com>.
on 8/16/01 4:32 PM, "Dan Cancro" <DC...@bridgespan.com> wrote:
> I just downloaded Turbine for the first time today and am trying to get it
> working with my Oracle 8i database. In step 7 of the Oracle 8i how-to page,
> http://jakarta.apache.org/turbine/howto/oracle-howto.html, it says that
> oracle-turbine.sql creates sequences for each table. I'm not seeing how it
> does this.
The default's are currently set to use the idbroker. You can use torque to
generate a version that uses sequences if you wish.
> Here are the contents of oracle-turbine.sql:
Gee...thanks for pasting a file here that we didn't need yet another copy
of...
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org