- 01 Mar, 2000 2 commits
-
-
Tom Lane authored
as independent clauses in the grammar. analyze.c takes care of putting the data where it belongs and complaining about invalid combinations. Also, make TEMP (and TEMPORARY) non-reserved words.
-
Tatsuo Ishii authored
-
- 29 Feb, 2000 1 commit
-
-
Jan Wieck authored
integrity triggers to after statement allways. Ignores deferred state now, closer to SQL3 semantics. Jan
-
- 28 Feb, 2000 8 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Byron Nikolaidis authored
such as BLCKSZ and MAXPGPATHLEN?
-
Bruce Momjian authored
-
Byron Nikolaidis authored
-
- 27 Feb, 2000 22 commits
-
-
Tom Lane authored
-
Tom Lane authored
-
Tom Lane authored
-
Bruce Momjian authored
-
Tom Lane authored
correctly (the lztext value will be promoted to text automatically).
-
Tom Lane authored
-
Bruce Momjian authored
-
Jan Wieck authored
into lztext. Jan
-
Tatsuo Ishii authored
-
Tatsuo Ishii authored
-
Tatsuo Ishii authored
-
Tatsuo Ishii authored
-
Tatsuo Ishii authored
-
Tom Lane authored
-
Tom Lane authored
relcache entry's reference count is zero.
-
Tom Lane authored
Shouldn't create any portability problems, since we have a configure test to #define away volatile if the compiler doesn't support it.
-
Tom Lane authored
-
Tom Lane authored
failures. Fix some outright bugs too, including a reference to uninitialized memory that would cause failures like this one: select -('1234567890.1234567'::text); ERROR: Unable to locate type oid 2139062143 in catalog
-
Tom Lane authored
This avoids the useless rebuild of pg_version that used to happen on each build or install pass.
-
Tom Lane authored
-
Tom Lane authored
-
Tom Lane authored
-
- 26 Feb, 2000 7 commits
-
-
Bruce Momjian authored
but we should get it out to beta testers.
-
Tom Lane authored
for Thomas to do the datetime consolidation before touching this, but it's done now...)
-
Tom Lane authored
a specific length or precision, such as foo::char(8). Remove erroneous removal of user-written casts at the top level of a SELECT target item.
-
Tom Lane authored
such as bpchar(char_expression, N), and pull out the attrtypmod that the function is coercing to. This allows correct deduction of the column type in examples such as CREATE VIEW v AS SELECT f1::char(8) FROM tbl; Formerly we labeled v's column as char-of-unknown-length not char(8). Also, this change causes the parser not to insert a redundant length coercion function if the user has explicitly casted an INSERT or UPDATE expression to the right length.
-
Tom Lane authored
fields, nor with bpchar and varchar fields that have typmod -1. The latter effectively have an unspecified length, so I made them display as char() and varchar() rather than falsely equating them to char(1) and varchar(1).
-
Tom Lane authored
refer to the single-byte char type. 7.0 was taking it as bpchar(1).
-
Tom Lane authored
It worked, because they both have fields named 'data', but it's surely trouble waiting to happen. I wonder whether there are more ...
-