github/jooq
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[#6357] Remove outdated section about Oracle not supporting IDENTITY columns

Browse Source
This commit is contained in:
lukaseder 2017-06-26 14:26:58 +02:00
parent 175c7e613f
commit 5ff9d4f8cc
13 changed files with 0 additions and 261 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
jOOQ-manual/src/main/resources/org/jooq/web/manual-2.5.xml
View File

@ -6483,27 +6483,6 @@ ID INTEGER IDENTITY(1,1) NOT NULL
id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-2.6.xml
View File

@ -7047,26 +7047,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.0.xml
View File

@ -8488,26 +8488,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.1.xml
View File

@ -9017,26 +9017,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.10.xml
View File

@ -12962,26 +12962,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.2.xml
View File

@ -9355,26 +9355,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.3.xml
View File

@ -10188,26 +10188,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.4.xml
View File

@ -11157,26 +11157,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.5.xml
View File

@ -11591,26 +11591,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.6.xml
View File

@ -11991,26 +11991,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.7.xml
View File

@ -12394,26 +12394,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.8.xml
View File

@ -12618,26 +12618,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>

20
jOOQ-manual/src/main/resources/org/jooq/web/manual-3.9.xml
View File

@ -12783,26 +12783,6 @@ id INTEGER IDENTITY NOT NULL
-- Sybase SQL Anywhere
id INTEGER NOT NULL IDENTITY]]></sql><html>
<p>
<strong>Oracle</strong>
</p>
<p>
Oracle does not know any identity columns at all. Instead, you will have to use a trigger and update the ID column yourself, using a custom sequence. Something along these lines:
</p>
</html><sql><![CDATA[CREATE OR REPLACE TRIGGER my_trigger
BEFORE INSERT
ON my_table
REFERENCING NEW AS new
FOR EACH ROW
BEGIN
SELECT my_sequence.nextval
INTO :new.id
FROM dual;
END my_trigger;]]></sql><html>
<p>
Note, that this approach can be employed in most databases supporting sequences and triggers! It is a lot more flexible than standard identities
</p>
</html></content>
</section>