- 24 Nov, 1997 1 commit
-
-
Bruce Momjian authored
-
- 21 Nov, 1997 1 commit
-
-
Bruce Momjian authored
-
- 20 Nov, 1997 1 commit
-
-
Bruce Momjian authored
-
- 02 Nov, 1997 1 commit
-
-
Vadim B. Mikheev authored
-
- 08 Sep, 1997 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.
-
- 07 Sep, 1997 1 commit
-
-
Bruce Momjian authored
-
- 22 Aug, 1997 1 commit
-
-
Bruce Momjian authored
-
- 19 Aug, 1997 1 commit
-
-
Bruce Momjian authored
-
- 31 May, 1997 1 commit
-
-
Vadim B. Mikheev authored
elog (WARN, "attribute %s not found", colname);
-
- 12 Mar, 1997 1 commit
-
-
Marc G. Fournier authored
Subject: [HACKERS] better access control error messages This patch replaces the 'no such class or insufficient privilege' with distinct error messages that tell you whether the table really doesn't exist or whether access was denied.
-
- 14 Feb, 1997 1 commit
-
-
Bruce Momjian authored
-
- 07 Feb, 1997 1 commit
-
-
Bruce Momjian authored
-
- 22 Jan, 1997 1 commit
-
-
Bruce Momjian authored
Invalidate vacuum relation cache to use new row counts from vacuum.
-
- 07 Dec, 1996 1 commit
-
-
Bruce Momjian authored
-
- 30 Nov, 1996 1 commit
-
-
Bruce Momjian authored
as ints and longs. Touches on quite a few function args as well. Most other files look ok as far as Oids go...still checking though... Since Oids are type'd as unsigned ints, they should prolly be used with the %ud format string in elog and sprintf messages. Not sure what kind of strangeness that could produce. Darren King
-
- 19 Nov, 1996 1 commit
-
-
Bruce Momjian authored
-
- 13 Nov, 1996 1 commit
-
-
Marc G. Fournier authored
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.
-
- 08 Nov, 1996 1 commit
-
-
Marc G. Fournier authored
From: Randy Terbush <randy@zyzzyva.com>
-
- 04 Nov, 1996 1 commit
-
-
Bruce Momjian authored
-
- 30 Oct, 1996 1 commit
-
-
Bruce Momjian authored
-
- 28 Aug, 1996 1 commit
-
-
Marc G. Fournier authored
-
- 13 Aug, 1996 1 commit
-
-
Marc G. Fournier authored
This patch forces postgres95 to assume any floating-point value is a float8. It removes the requirement that you cast all floating-point constants to float8. We can remove alot of casts in the regression test after we are sure this works. If I have missed anything, would someone let me know. I have tested inserts of floating-point values into float8 fields, and it worked well. Casting the number to float4 showed the same precision loss as previous uncast values showed. Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
-
- 19 Jul, 1996 1 commit
-
-
Marc G. Fournier authored
I have written some patches which add support for NULLs to Postgres95. In fact support for NULLs was already present in postgres, but it had been disabled because not completely debugged, I believe. My patches simply add some checks here and there. To enable the new code you must add -DNULL_PATCH to CFLAGS in Makefile.global. After recompiling you can do things like: insert into a (x, y) values (1, NULL); update a set x = NULL where x = 0; You can't still use a "where x=NULL" clause, you must use ISNULL instead. This could probably be an easy fix to do. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
-
- 09 Jul, 1996 1 commit
-
-
Marc G. Fournier authored
-