postgres

Commit Graph

Author	SHA1	Message	Date
Marc G. Fournier	07a65b2255	Commit of a MAJOR patch from Dan McGuirk <djm@indirect.com> Changes: * Unique index capability works using the syntax 'create unique index'. * Duplicate OID's in the system tables are removed. I put little scripts called 'duplicate_oids' and 'find_oid' in include/catalog that help to find and remove duplicate OID's. I also moved 'unused_oids' from backend/catalog to include/catalog, since it has to be in the same directory as the include files in order to work. * The backend tries converting the name of a function or aggregate to all lowercase if the original name given doesn't work (mostly for compatibility with ODBC). * You can 'SELECT NULL' to your heart's content. * I put my _bt_updateitem fix in instead, which uses _bt_insertonpg so that even if the new key is so big that the page has to be split, everything still works. * All literal references to system catalog OID's have been replaced with references to define'd constants from the catalog header files. * I added a couple of node copy functions. I think this was a preliminary attempt to get rules to work.	29 years ago
Marc G. Fournier	d93d3c843a	-Wall based cleanup of include files, based from acl.h, and everything that it depends on	29 years ago
Marc G. Fournier	ff36ebc922	More cleans of the inter-dependencies in the #include files	29 years ago
Bruce Momjian	f59a46a8c8	Parser Overhaul	29 years ago
Marc G. Fournier	f4ba64a0ac	Almost have access/common cleaned up...	29 years ago
Marc G. Fournier	6592bbaf08	wish there was an easier way to clean this up...	29 years ago
Marc G. Fournier	1054097464	More cleanups of the include files - centralizing to simplify the -I's required to compile	29 years ago
Marc G. Fournier	a2740a455f	There, now we support GiST...now what? :)	29 years ago
Marc G. Fournier	208a30f23d	The patch does several things: It adds a WITH OIDS option to the copy command, which allows dumping and loading of oids. If a copy command tried to load in an oid that is greater than its current system max oid, the system max oid is incremented. No checking is done to see if other backends are running and have cached oids. pg_dump as its first step when using the -o (oid) option, will copy in a dummy row to set the system max oid value so as rows are loaded in, they are certain to be lower than the system oid. pg_dump now creates indexes at the end to speed loading Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>	29 years ago
Marc G. Fournier	6c684b1847	Fixes: Previously Postgres95 wouldn't accept 'order by' clauses with fields referred to as '<table>.<field>', e.g.: select t1.field1, t2.field2 from table1 t1, table2 t2 order by t2.field2; This syntax is required by the ODBC SQL spec. Submitted by: Dan McGuirk <mcguirk@indirect.com>	30 years ago
Marc G. Fournier	ab22b34891	Fixes: While a normal SELECT statement can contain a GROUP BY clause, a cursor declaration cannot. This was not the case in PG-1.0. Was there a good reason why this was changed? Are cursors being phased out? Is there any way to get data with just a SELECT (and without a DECLARE CURSOR ...)? The patch below seems to fix things. If anyone can see a problem with it, please let me know. Thanks. Submitted by: David Smith <dasmith@perseus.tufts.edu>	30 years ago
Marc G. Fournier	d31084e9d1	Postgres95 1.01 Distribution - Virgin Sources	30 years ago

7 Commits (ec105b60263fee1c71f42532bdb5f482d65cab66)