b7064779f5
Updated copyright notice in header
2007-10-10 05:25:14 +00:00
f0dfc20124
Now we aren't guessing check constraint names
...
but getting the real ones under PostgreSQL. MDL-9356
2007-09-11 19:06:38 +00:00
a347e5e439
Preparing getCheckConstraintsFromDB() to retrieve the check constraint
...
defined for one field. Not used yet but I need it in CVS now.
2007-09-10 22:00:24 +00:00
4215e41ecb
Extending getCheckConstraintsFromDB() to support a new parameter
...
used to filter what field in the table we want to know
its check constraints
2007-09-09 16:28:16 +00:00
af999b9095
Temporary fix for MDL-9356 becuase it was blocking a bug I needed to fix. Eloy, please review carefully when you get back from holiday.
2007-08-17 09:59:54 +00:00
8101dccb8e
MDL-9920 Allowed xmldb to create 32-bit serial fields if specified, in postgres
2007-05-24 15:18:35 +00:00
9770914d5f
Now MySQL looks for existing index names. MDL-9256
...
Merged from MOODLE_18_STABLE
2007-04-08 22:59:54 +00:00
cfed9721ad
DB escaping comments. MDL-8918
...
Merged from MOODLE_18_STABLE
2007-03-15 19:03:07 +00:00
a1b2780c8e
Now Postgres naming of objects introspects to avoid duplicates. MDL-7376
2007-01-27 17:37:39 +00:00
d5eff6795e
Added support for getSequenceFromDB() to PG.
...
Merged from MOODLE_17_STABLE
2006-10-16 17:36:13 +00:00
906eebf6ad
Small change in rename_field() so objects won't become modified at all
...
in the process.
Merged from MOODLE_17_STABLE
2006-10-12 12:28:36 +00:00
2ddec1f4ac
Changed PG rename_index() to use the old ALTER TABLE ... RENAME TO syntax
...
(pretty strange syntax, but seems to work)
2006-10-03 15:00:55 +00:00
86bb076fc4
rename_field() under postgresql completed.
2006-10-02 17:02:35 +00:00
6c02f04b5a
rename_table() under postgresql completed
2006-10-02 16:27:18 +00:00
51517ddc6d
Avoid some double updates under PG
2006-10-01 16:02:09 +00:00
1f0c7fae15
Now PG adds fields in various steps is order to fulfill 7.4 min req
2006-10-01 15:48:29 +00:00
abf980a587
Now table renaming is working properly on PostgreSQL
...
(only renaming of check constraints are pending)
2006-10-01 08:44:55 +00:00
e77fd021e6
Implemented rename_key()
...
Note that this is one EXPERIMENTAL function and shouldn't be used
by you in production code EVER!
2006-09-30 19:43:16 +00:00
b899d9bf1d
Added support to change_field_enum() across all RDBMS
2006-09-30 17:03:17 +00:00
9af19c728d
Extendig use of new getTableName() over all generators
2006-09-30 12:13:07 +00:00
1a275daaaf
some more settings go to XMLDBGenerator (as they are default)
2006-09-28 18:31:28 +00:00
662244cb77
Deleting some parameters that aren't needed anymore. Code will
...
decide if creating underlying indexes for keys automatically now.
2006-09-28 17:02:49 +00:00
812e363a39
Now generators support to add/drop column defaults
2006-09-25 18:22:06 +00:00
ff936e2c2d
Finally PostgreSQL seems to be working now.... I've tried to do
...
it as clever as possible detecting when column specs change in
order to reduce the number of temp-update-drop-rename operations
2006-09-24 15:25:49 +00:00
b0ec41af8a
Prevent Unique Keys generation. Instead use unique indexes at DB level.
...
With this, all we'll have are PRIMARY KEYS + INDEXES, that are pretty
well supported by ADODB MetaXXX functions.
Both Unique and Foreign Keys will be used once ADODB support them and
the relational mode was enforced.
2006-09-24 09:38:56 +00:00
d4b86c90dc
Fixed bug about all chars being created with length 255. Penny found this!
2006-09-22 10:15:51 +00:00
eef868d17d
major whitespace cleanup - fixed trailng whitespace in new files and admin area
2006-09-20 21:00:45 +00:00
0dd87cfa7a
Delete one trailing comma
2006-09-12 22:15:44 +00:00
09942a5ec2
PGs doubles are caller DOUBLE PRECISION
2006-08-25 17:11:43 +00:00
860b55463f
Normalizing a bit all the float/double generators.
2006-08-22 22:10:09 +00:00
c8f85eeeba
Reducing the list of PG reserved words to the efectively
...
reserved words (the previous list included a lot of words
reserved by SQLXX standars but not by PG)
2006-08-21 12:04:48 +00:00
f9543de627
Since PostgreSQL 7.4 the precision given for float columsn is
...
the number of bits to use, and not the number of decimals. So,
based on the number of decimals from the XMLDB schema, we are
going to create REAL (<6 decimals) or DOUBLE PRECISION (>=6) columns.
2006-08-20 18:19:50 +00:00
9dcc6300a7
Now all the XMLDBxxx->geSQL functions return an array of statements to be
...
executed (easily to handle them in the installation/upgrade process
individually. Also, it's possible to specify one statement end.
2006-08-17 19:20:45 +00:00
6aa7885eb5
Minor adjustments to some comments.
2006-08-16 23:17:28 +00:00
ada5648103
Fixing some potential problems with prefixes and object names.
2006-08-16 23:01:46 +00:00
2ad7da9bec
Initial version of the postgres7 generator
2006-08-16 18:41:47 +00:00
nicolasconnault