- 04 7月, 2000 1 次提交
-
-
由 Tom Lane 提交于
Don't go through pg_exec_query_dest(), but directly to the execution routines. Also, extend parameter lists so that there's no need to change the global setting of allowSystemTableMods, a hack that was certain to cause trouble in the event of any error.
-
- 12 6月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 09 6月, 2000 2 次提交
-
-
由 Bruce Momjian 提交于
more restriction for fretful users. The current PG allow define only NO-CREATE-DB and NO-CREATE-USER restriction, but for some users I need NO-CREATE-TABLE and NO-LOCK-TABLE. This patch add to current code NOCREATETABLE and NOLOCKTABLE feature: CREATE USER username [ WITH [ SYSID uid ] [ PASSWORD 'password' ] ] [ CREATEDB | NOCREATEDB ] [ CREATEUSER | NOCREATEUSER ] -> [ CREATETABLE | NOCREATETABLE ] [ LOCKTABLE | NOLOCKTABLE ] ...etc. If CREATETABLE or LOCKTABLE is not specific in CREATE USER command, as default is set CREATETABLE or LOCKTABLE (true). A user with NOCREATETABLE restriction can't call CREATE TABLE or SELECT INTO commands, only create temp table is allow for him. Karel
-
由 Bruce Momjian 提交于
-
- 30 5月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 13 4月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 30 1月, 2000 1 次提交
-
-
由 Peter Eisentraut 提交于
Initdb help correction Changed end/abort to commit/rollback and changed related notices Commented out way old printing functions in libpq Fixed a typo in alter table / alter column
-
- 26 1月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
-
- 17 12月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
Jan
-
- 10 12月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 23 11月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
Make all system indexes unique. Make all cache loads use system indexes. Rename *rel to *relid in inheritance tables. Rename cache names to be clearer.
-
- 08 11月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
Fewer calls to nameout. Better use of RelationGetRelationName.
-
- 26 10月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
The following patch extends the COMMENT ON functionality to the rest of the database objects beyond just tables, columns, and views. The grammer of the COMMENT ON statement now looks like: COMMENT ON [ [ DATABASE | INDEX | RULE | SEQUENCE | TABLE | TYPE | VIEW ] <objname> | COLUMN <relation>.<attribute> | AGGREGATE <aggname> <aggtype> | FUNCTION <funcname> (arg1, arg2, ...) | OPERATOR <op> (leftoperand_typ rightoperand_typ) | TRIGGER <triggername> ON relname> Mike Mascari (mascarim@yahoo.com)
-
- 15 10月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
>From the ORACLE 7 SQL Language Reference Manual: ----------------------------------------------------- COMMENT Purpose: To add a comment about a table, view, snapshot, or column into the data dictionary. Prerequisites: The table, view, or snapshot must be in your own schema or you must have COMMENT ANY TABLE system privilege. Syntax: COMMENT ON [ TABLE table ] | [ COLUMN table.column] IS 'text' You can effectively drop a comment from the database by setting it to the empty string ''. ----------------------------------------------------- Example: COMMENT ON TABLE workorders IS 'Maintains base records for workorder information'; COMMENT ON COLUMN workorders.hours IS 'Number of hours the engineer worked on the task'; to drop a comment: COMMENT ON COLUMN workorders.hours IS ''; The current patch will simply perform the insert into pg_description, as per the TODO. And, of course, when the table is dropped, any comments relating to it or any of its attributes are also dropped. I haven't looked at the ODBC source yet, but I do know from an ODBC client standpoint that the standard does support the notion of table and column comments. Hopefully the ODBC driver is already fetching these values from pg_description, but if not, it should be trivial. Hope this makes the grade, Mike Mascari (mascarim@yahoo.com)
-
- 04 10月, 1999 1 次提交
-
-
由 Tom Lane 提交于
expressions in CREATE TABLE. There is no longer an emasculated expression syntax for these things; it's full a_expr for constraints, and b_expr for defaults (unfortunately the fact that NOT NULL is a part of the column constraint syntax causes a shift/reduce conflict if you try a_expr. Oh well --- at least parenthesized boolean expressions work now). Also, stored expression for a column default is not pre-coerced to the column type; we rely on transformInsertStatement to do that when the default is actually used. This means "f1 datetime default 'now'" behaves the way people usually expect it to. BTW, all the support code is now there to implement ALTER TABLE ADD CONSTRAINT and ALTER TABLE ADD COLUMN with a default value. I didn't actually teach ALTER TABLE to call it, but it wouldn't be much work.
-
- 24 9月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 19 9月, 1999 1 次提交
-
-
由 Tom Lane 提交于
additional argument specifying the kind of lock to acquire/release (or 'NoLock' to do no lock processing). Ensure that all relations are locked with some appropriate lock level before being examined --- this ensures that relevant shared-inval messages have been processed and should prevent problems caused by concurrent VACUUM. Fix several bugs having to do with mismatched increment/decrement of relation ref count and mismatched heap_open/close (which amounts to the same thing). A bogus ref count on a relation doesn't matter much *unless* a SI Inval message happens to arrive at the wrong time, which is probably why we got away with this sloppiness for so long. Repair missing grab of AccessExclusiveLock in DROP TABLE, ALTER/RENAME TABLE, etc, as noted by Hiroshi. Recommend 'make clean all' after pulling this update; I modified the Relation struct layout slightly. Will post further discussion to pghackers list shortly.
-
- 18 7月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 16 7月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 26 5月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 2月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 04 2月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 02 2月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 12月, 1998 1 次提交
-
-
由 Marc G. Fournier 提交于
Initial attempt to clean up the code... Switch sprintf() to snprintf() Remove any/all #if 0 -or- #ifdef NOT_USED -or- #ifdef FALSE sections of code
-
- 28 11月, 1998 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 02 10月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 01 9月, 1998 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 19 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
no longer returns buffer pointer, can be gotten from scan; descriptor; bootstrap can create multi-key indexes; pg_procname index now is multi-key index; oidint2, oidint4, oidname are gone (must be removed from regression tests); use System Cache rather than sequential scan in many places; heap_modifytuple no longer takes buffer parameter; remove unused buffer parameter in a few other functions; oid8 is not index-able; remove some use of single-character variable names; cleanup Buffer variables usage and scan descriptor looping; cleaned up allocation and freeing of tuples; 18k lines of diff;
-
- 06 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
files. Fix sequence creation hack for relkind type.
-
- 16 6月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 26 4月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 4月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 31 3月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
1. Remove the char2, char4, char8 and char16 types from postgresql 2. Change references of char16 to name in the regression tests. 3. Rename the char16.sql regression test to name.sql. 4. Modify the regression test scripts and outputs to match up. Might require new regression.{SYSTEM} files... Darren King
-
- 26 2月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 10 2月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 06 1月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 05 1月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-