aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser
Commit message (Collapse)AuthorAge
...
* Move IN to proper place.Bruce Momjian1999-05-17
|
* CleanupBruce Momjian1999-05-17
|
* Require IN in LOCK syntax.Bruce Momjian1999-05-17
|
* Add double quotes around the sequence name generated to support theThomas G. Lockhart1999-05-13
| | | | | | SERIAL data type DEFAULT clause. This fixes a problem finding the sequence name when mixed case table names are involved.
* Surround a variable declaration with ENABLE_OUTER_JOINS to suppressThomas G. Lockhart1999-05-13
| | | | compiler warnings about an unused variable.
* Rip out QueryTreeList structure, root and branch. QuerytreeTom Lane1999-05-13
| | | | | | | | | | 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.
* Replaced targetlist entry in GroupClause by reference numberJan Wieck1999-05-12
| | | | | | | in Resdom and GroupClause so changing of resno's doesn't confuse the grouping any more. Jan
* Add keywords to implement Vadim's transaction isolationThomas G. Lockhart1999-05-12
| | | | | | | | | | 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.
* Fix problem with multiple indices defined if using column- and table-Thomas G. Lockhart1999-05-12
| | | | | | | 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.
* Handle conversion of floating point constants to internal strings.Thomas G. Lockhart1999-05-12
|
* Keep long non-quoted numeric strings *as* untyped strings if they failThomas G. Lockhart1999-05-12
| | | | | | the obvious conversion. Define a new pattern "decimal" which is non-exponential floating point for use with numeric() and decimal() types.
* clean up commentsBruce Momjian1999-05-11
|
* Change error messages to oids come out as %u and not %d. Change has noBruce Momjian1999-05-10
| | | | real affect now.
* here are some patches for 6.5.0 which I already submitted but have neverBruce Momjian1999-05-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Defend against 'update oid'. Someday we might want to supportTom Lane1999-04-29
| | | | | that, but it'd be a New Feature, wouldn't it ... in the meantime, avoiding a backend crash seems worthwhile.
* Aggregate functions didn't work on subscripted array references.Tom Lane1999-04-29
| | | | Things are better now.
* Fixed DECIMAL data type to handle specified precision in atttypmodJan Wieck1999-04-27
| | | | Jan
* Add disk space message to "can not extend" message.Bruce Momjian1999-04-23
|
* Add temporary for temp.Bruce Momjian1999-04-19
|
* Fix problems seen when result of a subselect was used in anTom Lane1999-04-19
| | | | | | | expression context (ie, not at the top level of a WHERE clause). Examples like this one work now: SELECT name, value FROM t1 as touter WHERE (value/(SELECT AVG(value) FROM t1 WHERE name = touter.name)) > 0.75;
* After transforming a CASE expr with a default argument,Tom Lane1999-04-18
| | | | | | | | delete the default argument from the node. This prevents the executor from spitting up on the untransformed argument expression. Typical failure was: select (case f1 when 'val' then 'subst' else f1 end) from t1; ERROR: copyObject: don't know how to copy 704
* Add % to b_expr.Bruce Momjian1999-03-22
|
* Add .cvsignore file so cvs doesn't complain if you have lex/yaccTom Lane1999-03-21
| | | | output files laying about.
* cleanupBruce Momjian1999-03-21
|
* Fix for %4 and 4%.Bruce Momjian1999-03-21
|
* Remove yacc/lex output files from CVS repository.Tom Lane1999-03-20
|
* Reverse out pfree agg part of patch from Erik Riedel.Bruce Momjian1999-03-20
|
* Fix shift/reduce for NULL = Var.Bruce Momjian1999-03-19
|
* cleanup parserBruce Momjian1999-03-18
|
* grammar cleanup'Bruce Momjian1999-03-18
|
* cleanup of grammer.Bruce Momjian1999-03-18
|
* Fix optimizer indexing not working for negative numbers.Bruce Momjian1999-03-18
|
* Add new postgres -O option to allow system table structure changes.Bruce Momjian1999-03-17
|
* Left associates all operators, instead of non-associating them.Bruce Momjian1999-03-17
|
* Have % operator have precedence like /.Bruce Momjian1999-03-17
|
* Update nextval() code.Bruce Momjian1999-03-16
|
* Fix snprintf with strings, and nextval('"Aa"');Bruce Momjian1999-03-16
|
* cleanupBruce Momjian1999-03-15
|
* Allow sequence nextval actions to be case-sensitive.Bruce Momjian1999-03-15
|
* Cleanup of hash functions in pg_proc.Bruce Momjian1999-03-14
|
* I have a problem with Access97 not working properly when entering newBruce Momjian1999-03-14
| | | | | | | | | | | | | | records using a sub form, i.e. entering a new order/orderlines or master and detail tables. The problem is caused by a SQL statement that Access97 makes involving NULL. The syntax that fails is "column_name" = NULL. The following attachment was provided by -Jose'-. It contains a very small enhancement to gram.y that will allow Access97 to work properly with sub forms. Can this enhancement be added to release 6.5? <<gram.patch>> Thanks, Michael
* Really remove Recipe.Bruce Momjian1999-03-07
|
* Someone forgot to commit gram.c and parse.h after his latestTom Lane1999-02-27
| | | | set of updates to gram.y.
* Clean up error messages.Thomas G. Lockhart1999-02-23
|
* Do a better job of selecting candidates among functionsThomas G. Lockhart1999-02-23
| | | | | when no exact match. Clean up elog error messages.
* Include some new code for outer joins. Disabled by default, but enable byThomas G. Lockhart1999-02-23
| | | | | including the following in your Makefile.custom: CFLAGS+= -DENABLE_OUTER_JOINS -DEXEC_MERGEJOINDEBUG
* Put in explicit checks for implicit index name lengths.Thomas G. Lockhart1999-02-23
| | | | | Put in hooks for outer joins by passing a few parameters back and forth in function calls. May not be close to working yet.
* Modify the outer join placeholder code with something closer to workingThomas G. Lockhart1999-02-23
| | | | code. Works here, but not completely implemented past this point.
* Final optimizer cleanups.Bruce Momjian1999-02-22
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-02-21
| | | | | | Ok. I made patches replacing all of "#if FALSE" or "#if 0" to "#ifdef NOT_USED" for current. I have tested these patches in that the postgres binaries are identical.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 02:30:18 +0000