- 16 Nov, 2001 8 commits
-
-
Tom Lane authored
-
Peter Eisentraut authored
and comment in src/backend/parser/Makefile for the technical details.
-
Tom Lane authored
discussions in pghackers.
-
Peter Eisentraut authored
-
Michael Meskes authored
-
Hiroshi Inoue authored
-
Tom Lane authored
mutually exclusive keyword lists spanning all known keywords --- including AS. Moved COALESCE and a few other ColLabels into the can-be-ColId list.
-
Tom Lane authored
-
- 15 Nov, 2001 12 commits
-
-
Tom Lane authored
round of editorial effort.
-
Tom Lane authored
to reverse-engineer documentation for them.
-
Bruce Momjian authored
-
Tom Lane authored
-
Bruce Momjian authored
int8, int16, int32, int64 and separately uint8, uint16, uint32, uint64 The previous patch grouped: int8, int16 and int32 uint8, uint16 and uint32 int64 and uint64 <-- this grouping is wrong on AIX 4.3.3 and below If you prefer to make 4 groups out of this you could apply this patch. Andreas
-
Bruce Momjian authored
-
Bruce Momjian authored
Peter E, Tatsuo, Andreas
-
Peter Eisentraut authored
-
Tom Lane authored
-
Tatsuo Ishii authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 14 Nov, 2001 7 commits
-
-
Tom Lane authored
with reality, and add doco for Jan's recent round of enhancements.
-
Tom Lane authored
in C, but recommend that newbies who don't recognize this trick should do some studying ...
-
Bruce Momjian authored
-
Dave Cramer authored
-
Bruce Momjian authored
-
Michael Meskes authored
-
Barry Lind authored
There's also a little fix for the getRow() method. While fixing absolute(), I noticed that getRow() wasn't quite following the spec: it wasn't returning 0 when the ResultSet wasn't positioned on a row. I've started a ResultSet test case and included it as well. Liam Stewart
-
- 13 Nov, 2001 5 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Tom Lane authored
destination in plpgsql.
-
Bruce Momjian authored
-
- 12 Nov, 2001 8 commits
-
-
Tom Lane authored
bpchar, bit, numeric with typmod -1. Alter format_type so that this representation is printed when the typmod is -1. This ensures that tables having such columns can be pg_dump'd and reloaded correctly. Also, remove the rather useless and non-SQL-compliant default precision and scale for type NUMERIC. A numeric column declared as such (with no precision/scale) will now have typmod -1 which means that numeric values of any precision/scale can be stored in it, without conversion to a uniform scale. This seems significantly more useful than the former behavior. Part of response to bug #513.
-
Bruce Momjian authored
-
Tom Lane authored
use that typmod not -1 as the typmod of the CASE result. Part of response to bug#513.
-
Tom Lane authored
typmod of a particular column, mark the output with that same typmod, not -1 as formerly. -1 is still used if there is any disagreement. Part of response to bug#513.
-
Barry Lind authored
fixed bug in ResultSet. Version 1.29 backed out two previous fixes (1.26 and 1.25). This checkin add back those two previous fixes. Problem reported by Daniel Germain
-
Peter Eisentraut authored
-
Barry Lind authored
Commit to support MD5 passwords as per the backend for 7.2. This patch was submitted by Jeremy Wohl jeremyw-pgjdbc@igmus.org
-
Bruce Momjian authored
andrea gelmini
-