Lukas Eder
d80ccddec0
[ jOOQ/jOOQ#12110 ] Move Sakila database to own repository
2021-07-06 09:42:43 +02:00
Lennart Jonsson
2ec2de548a
Add empty comment after stmt in trigger. This makes it possible to run script from clp without changing stmt terminator
2020-06-08 09:45:06 +02:00
Gerald Venzl
2eb35d6cd0
Add verification steps after data load
...
Signed-off-by: Gerald Venzl <gerald.venzl@gmail.com>
2020-03-10 21:21:15 -07:00
Gerald Venzl
ea7124de77
Add ReadMe with install instructions
...
Signed-off-by: Gerald Venzl <gerald.venzl@gmail.com>
2020-03-10 21:08:10 -07:00
Gerald Venzl
3271b0073e
Add commit, disable/enable constraints
...
Signed-off-by: Gerald Venzl <gerald.venzl@gmail.com>
2020-03-10 21:05:37 -07:00
Gerald Venzl
b88d59c206
add commits, graceful constraints
...
Add commits after each table to avoid unnecessary UNDO tablespace growth due to one big transaction
DISABLE and ENABLE constraints rather than DROP and CREATE so taht constraint definition remains in schema.sql alone
Signed-off-by: Gerald Venzl <gerald.venzl@gmail.com>
2020-03-10 21:04:44 -07:00
Gerald Venzl
ecdda13f60
Remove redunant / (only needed for PL/SQL)
...
Signed-off-by: Gerald Venzl <gerald.venzl@gmail.com>
2020-03-10 21:01:48 -07:00
Roland Weisleder
63588967b9
Sakila/PostgreSQL: Don't fail if language plpgsql already exists
...
When using the Sakila DB with the Docker image postgres:12.1 the
initialisation fails with:
ERROR: language "plpgsql" already exists
With PostgreSQL 8.4 (see [1]) and earlier it was only possible to
execute:
CREATE [ PROCEDURAL ] LANGUAGE name
Starting with PostgreSQL 9.0 (see [2]) it is possible to execute:
CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE name
This commit makes the SQL script incompatible with PostgreSQL 8.4
and earlier.
[1] https://www.postgresql.org/docs/8.4/sql-createlanguage.html
[2] https://www.postgresql.org/docs/9.0/sql-createlanguage.html
2019-12-26 13:15:17 +01:00
Maximilian Rehkopf
2a9a29743f
Sakila/PostgreSQL: Replace nonexisting IF with CASE
2019-05-17 13:56:30 +02:00
lukaseder
d6ef24811f
[ #8400 ] Fixed PostgreSQL Sakila deletion script
2019-03-26 14:40:57 +01:00
lukaseder
113a4ed033
[ #8235 ] Improve Sakila database example scripts
2019-01-22 10:13:49 +01:00
lukaseder
b2b174cc2d
[ #8235 ] Improve Sakila database example scripts
2019-01-22 10:13:42 +01:00
lukaseder
c2029a434c
[ #8047 ] Error Importing Sakila database in Oracle Express 11g
2018-11-19 12:25:02 +01:00
Lukas Eder
b9c3f1aa99
Update ReadME.txt
2017-12-29 17:48:57 +01:00
Lukas Eder
a791329291
Delete ReadME.txt
2017-12-29 17:48:36 +01:00
Lukas Eder
650482a9ab
Delete access-sakila.mdb
2017-12-29 17:48:25 +01:00
Prasanth Jayachandran
78b2bbf556
staff.picture column data is too long for mysql
2017-10-31 01:19:30 -07:00
lukaseder
7e7eb2c4ed
[ #6368 ] Port Sakila database to DB2
2017-06-30 14:31:31 +02:00
Ralf Stubner
56358011d9
SQL Server compatability
...
- add GO after DB creation
- fix datetime formating
2017-05-10 18:41:39 +02:00
lukaseder
e226b8e61e
Make all PKs in Sakila NONCLUSTERED
2016-12-04 12:11:23 +01:00
Lukas Eder
0658eae613
[ #330 ] Add example Package with RECORD types to the Sakila database
2016-11-01 15:33:15 +01:00
Lukas Eder
52a7138483
Give all primary keys a name
2016-10-20 10:14:30 +02:00
Lukas Eder
be073bea2c
Fixed sakila scripts
2015-09-08 14:32:00 +02:00
Lukas Eder
56a07b060b
[ #3701 ] Add some Sakila-based examples
2014-10-20 11:36:17 +02:00
