- 04 Jan, 2002 9 commits
-
-
Bruce Momjian authored
< perhaps CREATE DATABASE dbname WITH USER = "user" (Gavin) --- > perhaps CREATE DATABASE dbname WITH OWNER = "user" (Gavin)
-
Bruce Momjian authored
> * Allow command blocks that can ignore certain types of errors
-
Tom Lane authored
-
Thomas G. Lockhart authored
Move some tabular information on these from the chapter on data types to the appendix on dates and times.
-
Thomas G. Lockhart authored
Fixes time zone problems introduced by Thomas' implementation of TIMESTAMP WITHOUT TIME ZONE which caused the behavior of the previously appropriate routine, timestamp_date(), to change for the worse in this context.
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
< perhaps CREATE DATABASE dbname WITH USER = "user" --- > perhaps CREATE DATABASE dbname WITH USER = "user" (Gavin)
-
Bruce Momjian authored
< * Allow only owner to create indexes
-
- 03 Jan, 2002 28 commits
-
-
Tom Lane authored
Disallow CREATE INDEX on system catalogs, non-tables (views, sequences, etc). Disallow CREATE/DROP TRIGGER on system catalogs, non-tables. Disallow ALTER TABLE ADD/DROP CONSTRAINT on system catalogs. Disallow FOREIGN KEY reference to non-table. None of these things can actually work in the present system structure, but the code was letting them pass without complaint.
-
Tom Lane authored
start up, wait until a psql connection attempt succeeds. Per gripe from Jason Tishler.
-
Bruce Momjian authored
< allow error codes to be specified; requires nested transactions --- > allow error codes to be specified; requires savepoints 321c321 < * Allow nested transactions / savepoints [transactions] --- > * Allow savepoints / nested transactions [transactions]
-
Bruce Momjian authored
< allow error codes to be specified --- > allow error codes to be specified; requires nested transactions
-
Tom Lane authored
portal's memory context, so that they will live as long as the portal does.
-
Bruce Momjian authored
> o Allow COPY to report error lines and continue; optionally > allow error codes to be specified
-
Bruce Momjian authored
> * Make equals sign optional in CREATE DATABASE WITH param = 'val'
-
Bruce Momjian authored
> * Prevent create/drop scripts from allowing extra args (Bruce)
-
Tom Lane authored
-
Bruce Momjian authored
> * Allow only owner to create indexes
-
Bruce Momjian authored
< * Add config file check for $ODBCINI, $HOME/.odbc.ini, and /etc/odbc.ini --- > * Add config file check for $ODBCINI, $HOME/.odbc.ini, installpath/etc/odbc.ini
-
Bruce Momjian authored
-
Bruce Momjian authored
Took test from createlang.
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
> * Add config file check for $ODBCINI, $HOME/.odbc.ini, and /etc/odbc.ini
-
Bruce Momjian authored
> * Make it easier to create a database owned by someone who can't createdb, > perhaps CREATE DATABASE dbname WITH USER = "user"
-
Bruce Momjian authored
wrote: > > > Just testing pgcrypto on freebsd/alpha. I get some warnings: > > They should be harmless, although I should fix them. > > The actual code is: > > if ((dlen & 15) || (((unsigned) res) & 3)) > return -1; > Hard to imagine how (uint *) & 3 makes any sense, unless res isn't > always a (uint8 *). Is that true? At some point it was casted to (uint32*) so I wanted to be sure its ok. ATM its pointless. Please apply the following patch. -- marko
-
Bruce Momjian authored
tables.
-
Bruce Momjian authored
not work. Fixed to match createlang.
-
Bruce Momjian authored
-
Bruce Momjian authored
< o Move to using 'make' rather than 'ant'(?) --- > o Support both 'make' and 'ant'
-
Bruce Momjian authored
-
Bruce Momjian authored
existing code of dbname optional actually work.
-
Bruce Momjian authored
< * Change 'createlang [langname] dbname' to 'createlang langname [dbname]'
-
Bruce Momjian authored
> * Change 'createlang [langname] dbname' to 'createlang langname [dbname]'
-
Tom Lane authored
per bug report from Laurette Cisneros.
-
- 02 Jan, 2002 2 commits
- 01 Jan, 2002 1 commit
-
-
Tom Lane authored
macros, but only at explicit CHECK_FOR_INTERRUPTS() calls. Not clear whether overenthusiastic acceptance of interrupts accounts for any real bugs, but it definitely seems risky and unnecessary.
-