- 19 6月, 1999 1 次提交
-
-
由 Tom Lane 提交于
is parse_aggs.c. This fixes its failure to cope with (at least) CaseExpr and ArrayRef nodes, which is the reason why both of these fail in 6.5: select coalesce(f1,0) from int4_tbl group by f1; ERROR: Illegal use of aggregates or non-group column in target list select sentence.words[0] from sentence group by sentence.words[0]; ERROR: Illegal use of aggregates or non-group column in target list The array case still fails, but at least it's not parse_agg's fault anymore ... considering that we now support CASE officially, I think it's important to fix the first example ...
-
- 18 6月, 1999 1 次提交
-
-
由 Tom Lane 提交于
used to overrun its fixed-size arrays before detecting error; not cool). Also, replace uses of magic constant '8' with 'MAXFARGS'.
-
- 07 6月, 1999 1 次提交
-
-
由 Tom Lane 提交于
a non-leading % would be put into the >=/<= patterns. Also, repair longstanding confusion about whether %% means a literal %%. The SQL92 doesn't say any such thing, and textlike() knows that, but gram.y didn't.
-
- 06 6月, 1999 1 次提交
-
-
由 Tom Lane 提交于
index, etc is too long, truncate until it fits.
-
- 29 5月, 1999 1 次提交
-
-
由 Tom Lane 提交于
few percent speedup in INSERT...
-
- 26 5月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 24 5月, 1999 2 次提交
- 22 5月, 1999 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 21 5月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 20 5月, 1999 3 次提交
-
-
由 Jan Wieck 提交于
SelectStmt and CursorStmt tried to parse FOR UPDATE ... / FOR READ ONLY. Cursor now checks that it is read only by looking at forUpdate of Query. SelectStmt handles FOR READ ONLY too. Jan
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 19 5月, 1999 1 次提交
-
-
由 Tom Lane 提交于
will pass through rather than spitting up. This is necessary to handle cases where coerce_type causes a subexpression to be retransformed, as in SELECT count(*) + 1.0 FROM table
-
- 18 5月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 17 5月, 1999 5 次提交
-
-
由 Tom Lane 提交于
for SERIAL column's constraint, but forgot to increase space palloc'd...
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 13 5月, 1999 3 次提交
-
-
由 Thomas G. Lockhart 提交于
SERIAL data type DEFAULT clause. This fixes a problem finding the sequence name when mixed case table names are involved.
-
由 Thomas G. Lockhart 提交于
compiler warnings about an unused variable.
-
由 Tom Lane 提交于
lists are now plain old garden-variety Lists, allocated with palloc, rather than specialized expansible-array data allocated with malloc. This substantially simplifies their handling and eliminates several sources of memory leakage. Several basic types of erroneous queries (syntax error, attempt to insert a duplicate key into a unique index) now demonstrably leak zero bytes per query.
-
- 12 5月, 1999 5 次提交
-
-
由 Jan Wieck 提交于
in Resdom and GroupClause so changing of resno's doesn't confuse the grouping any more. Jan
-
由 Thomas G. Lockhart 提交于
and lock syntax as fully parsed tokens. Two keywords for isolation are non-reserved SQL92 (COMMITTED, SERIALIZABLE). All other new keywords are non-reserved Postgres (not SQL92) (ACCESS, EXCLUSIVE, MODE, SHARE). Add syntax to allow CREATE [GLOBAL|LOCAL] TEMPORARY TABLE, throwing an error if GLOBAL is specified.
-
由 Thomas G. Lockhart 提交于
constraints. Reported by Tom Lane. Now, check for duplicate indices and retain the one which is a primary-key. Adjust elog NOTICE messages to surround table and column names with single quotes.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
the obvious conversion. Define a new pattern "decimal" which is non-exponential floating point for use with numeric() and decimal() types.
-
- 11 5月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 10 5月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
real affect now.
-
- 04 5月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
been applied. The patches are in the .tar.gz attachment at the end: varchar-array.patch this patch adds support for arrays of bpchar() and varchar(), which where always missing from postgres. These datatypes can be used to replace the _char4, _char8, etc., which were dropped some time ago. block-size.patch this patch fixes many errors in the parser and other program which happen with very large query statements (> 8K) when using a page size larger than 8192. This patch is needed if you want to submit queries larger than 8K. Postgres supports tuples up to 32K but you can't insert them because you can't submit queries larger than 8K. My patch fixes this problem. The patch also replaces all the occurrences of `8192' and `1<<13' in the sources with the proper constants defined in include files. You should now never find 8192 hardwired in C code, just to make code clearer. -- Massimo Dal Zotto
-
- 29 4月, 1999 2 次提交