aboutsummaryrefslogtreecommitdiff
path: root/src/include/parser
Commit message (Collapse)AuthorAge
* Remove bogus code in oper_exact --- if it didn't find an exactTom Lane1999-08-23
| | | | | | | | | match then it tried for a self-commutative operator with the reversed input data types. This is pretty silly; there could never be such an operator, except maybe in binary-compatible-type scenarios, and we have oper_inexact for that. Besides which, the oprsanity regress test would complain about such an operator. Remove nonfunctional code and simplify routine calling convention accordingly.
* Major revision of sort-node handling: push knowledge of queryTom Lane1999-08-21
| | | | | | | | | | | | | sort order down into planner, instead of handling it only at the very top level of the planner. This fixes many things. An explicit sort is now avoided if there is a cheaper alternative (typically an indexscan) not only for ORDER BY, but also for the internal sort of GROUP BY. It works even when there is no other reason (such as a WHERE condition) to consider the indexscan. It works for indexes on functions. It works for indexes on functions, backwards. It's just so cool... CAUTION: I have changed the representation of SortClause nodes, therefore THIS UPDATE BREAKS STORED RULES. You will need to initdb.
* Revise parse_coerce() to handle coercion of int and floatTom Lane1999-08-05
| | | | | constants, not only string constants, at parse time. Get rid of parser_typecast2(), which is bogus and redundant...
* Rewrite parser's handling of INSERT ... SELECT so that processingTom Lane1999-07-19
| | | | | | | | | of the SELECT part of the statement is just like a plain SELECT. All INSERT-specific processing happens after the SELECT parsing is done. This eliminates many problems, e.g. INSERT ... SELECT ... GROUP BY using the wrong column labels. Ensure that DEFAULT clauses are coerced to the target column type, whether or not stored clause produces the right type. Substantial cleanup of parser's array support.
* More cleanupBruce Momjian1999-07-16
|
* Change #include's to use <> and "" as appropriate.Bruce Momjian1999-07-15
|
* Clean up #include in /include directory. Add scripts for checking includes.Bruce Momjian1999-07-15
|
* Cleanup of /include #include's, for 6.6 only.Bruce Momjian1999-07-14
|
* Remove S*I comments from Stephan.Bruce Momjian1999-07-13
|
* Defend against function calls with more than 8 arguments (codeTom Lane1999-06-17
| | | | | used to overrun its fixed-size arrays before detecting error; not cool). Also, replace uses of magic constant '8' with 'MAXFARGS'.
* Avoid redundant SysCache searches in coerce_type, for anotherTom Lane1999-05-29
| | | | few percent speedup in INSERT...
* Make functions static or NOT_USED as appropriate.Bruce Momjian1999-05-26
|
* Another pgindent run. Sorry folks.Bruce Momjian1999-05-25
|
* pgindent run over code.Bruce Momjian1999-05-25
|
* Fix for DEFAULT ''.Bruce Momjian1999-05-22
|
* Change resjunk to a boolean.Bruce Momjian1999-05-17
|
* 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.
* Make type 'regproc' binary-compatible with int4 and oid,Tom Lane1999-03-10
| | | | | so that it has some SQL operators available. It's difficult to write automated tests of a data type that you haven't even got == for...
* Add parameters to function calls to pass back table qualifications.Thomas G. Lockhart1999-02-23
|
* Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian1999-02-13
|
* Remove equivalence between datetime and float8. Led to nothin' but trouble.Thomas G. Lockhart1999-02-13
|
* Rename Aggreg to Aggref.Bruce Momjian1999-01-24
|
* Hi!Bruce Momjian1999-01-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INTERSECT and EXCEPT is available for postgresql-v6.4! The patch against v6.4 is included at the end of the current text (in uuencoded form!) I also included the text of my Master's Thesis. (a postscript version). I hope that you find something of it useful and would be happy if parts of it find their way into the PostgreSQL documentation project (If so, tell me, then I send the sources of the document!) The contents of the document are: -) The first chapter might be of less interest as it gives only an overview on SQL. -) The second chapter gives a description on much of PostgreSQL's features (like user defined types etc. and how to use these features) -) The third chapter starts with an overview of PostgreSQL's internal structure with focus on the stages a query has to pass (i.e. parser, planner/optimizer, executor). Then a detailed description of the implementation of the Having clause and the Intersect/Except logic is given. Originally I worked on v6.3.2 but never found time enough to prepare and post a patch. Now I applied the changes to v6.4 to get Intersect and Except working with the new version. Chapter 3 of my documentation deals with the changes against v6.3.2, so keep that in mind when comparing the parts of the code printed there with the patched sources of v6.4. Here are some remarks on the patch. There are some things that have still to be done but at the moment I don't have time to do them myself. (I'm doing my military service at the moment) Sorry for that :-( -) I used a rewrite technique for the implementation of the Except/Intersect logic which rewrites the query to a semantically equivalent query before it is handed to the rewrite system (for views, rules etc.), planner, executor etc. -) In v6.3.2 the types of the attributes of two select statements connected by the UNION keyword had to match 100%. In v6.4 the types only need to be familiar (i.e. int and float can be mixed). Since this feature did not exist when I worked on Intersect/Except it does not work correctly for Except/Intersect queries WHEN USED IN COMBINATION WITH UNIONS! (i.e. sometimes the wrong type is used for the resulting table. This is because until now the types of the attributes of the first select statement have been used for the resulting table. When Intersects and/or Excepts are used in combination with Unions it might happen, that the first select statement of the original query appears at another position in the query which will be executed. The reason for this is the technique used for the implementation of Except/Intersect which does a query rewrite!) NOTE: It is NOT broken for pure UNION queries and pure INTERSECT/EXCEPT queries!!! -) I had to add the field intersect_clause to some data structures but did not find time to implement printfuncs for the new field. This does NOT break the debug modes but when an Except/Intersect is used the query debug output will be the already rewritten query. -) Massive changes to the grammar rules for SELECT and INSERT statements have been necessary (see comments in gram.y and documentation for deatails) in order to be able to use mixed queries like (SELECT ... UNION (SELECT ... EXCEPT SELECT)) INTERSECT SELECT...; -) When using UNION/EXCEPT/INTERSECT you will get: NOTICE: equal: "Don't know if nodes of type xxx are equal". I did not have time to add comparsion support for all the needed nodes, but the default behaviour of the function equal met my requirements. I did not dare to supress this message! That's the reason why the regression test for union will fail: These messages are also included in the union.out file! -) Somebody of you changed the union_planner() function for v6.4 (I copied the targetlist to new_tlist and that was removed and replaced by a cleanup of the original targetlist). These chnages violated some having queries executed against views so I changed it back again. I did not have time to examine the differences between the two versions but now it works :-) If you want to find out, try the file queries/view_having.sql on both versions and compare the results . Two queries won't produce a correct result with your version. regards Stefan
* Define routines and catalog entries for string min()/max() functions.Thomas G. Lockhart1998-12-08
| | | | Extend new type coersion techniques to aggregates.
* Remove duplicate CIDR funcs by using coerce entries.Bruce Momjian1998-10-22
|
* Make functions static or ifdef NOT_USED. Prevent pg_version creation.Bruce Momjian1998-10-08
|
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-01
|
* Make sure resdomno for update/insert match attribute number forBruce Momjian1998-08-25
| | | | | rewrite system. Restructure parse_target to make it easier to understand.
* Include OID as a built-in type.Thomas G. Lockhart1998-08-14
|
* From: David Hartwig <daybee@bellatlantic.net>Marc G. Fournier1998-08-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I have attached a patch to allow GROUP BY and/or ORDER BY function or expressions. Note worthy items: 1. The expression or function need not be in the target list. Example: SELECT name FROM foo GROUP BY lower(name); 2. Simplified the grammar to use expressions only. 3. Cleaned up earlier patch in this area to make use of existing utility functions. 3. Reduced some of the members in the SortGroupBy parse node. The original data members were redundant with the new expression node. (MUST do a "make clean" now) 4. Added a new parse node "JoinUsing". The JOIN USING clause was overloading this SortGroupBy structure. With the afore mentioned reduction of members, the two clauses lost all their commonality. 5. A bug still exist where, if a function or expression is GROUPed BY, and an aggregate function does not include a attribute from the expression or function, the backend crashes. (or something like that) The bug pre-dates this patch. Example: SELECT lower(a) AS lowcase, count(b) FROM foo GROUP BY lowcase; *** BOOM *** --Also when not in target list SELECT count(b) FROM foo GROUP BY lower(a); *** BOOM AGAIN ***
* Change atttypmod from int16 to int32, for Thomas.Bruce Momjian1998-07-12
|
* Include int8 as a built-in data type.Thomas G. Lockhart1998-07-08
| | | | | Merge "resjunk" handling with automatic type conversion when selecting from another column.
* I made several adjustments to my earlier patch to handle theBruce Momjian1998-06-05
| | | | condition where the target label is ambiguous.
* Define new routines oper_exact() and oper_inexact().Thomas G. Lockhart1998-05-29
| | | | Add coerce_target_expr().
* Add func_select_candidate() to allow use in unary operator parsing.Thomas G. Lockhart1998-05-29
|
* Add NAMEOID as built-in type.Thomas G. Lockhart1998-05-29
| | | | | | Change ordering of IS_BUILTIN_TYPE() macro to optimize lookup. Make CASH type _not_ equivalent to INT4. CASH is passed by reference rather than passed by value.
* From: David Hartwig <daveh@insightdist.com>Marc G. Fournier1998-05-21
| | | | | Here is a patch to remove the requirement that ORDER/GROUP BY clause identifiers be included in the target list.
* Add capabilities for automatic type conversion.Thomas G. Lockhart1998-05-09
|
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-26
|
* Atttypmod cleanup.Bruce Momjian1998-02-13
|
* Pass around typmod as int16.Bruce Momjian1998-02-10
|
* Pass attypmod through to executor by adding to Var and Resdom.Bruce Momjian1998-02-10
|
* func_error() changed so that if caller is passed with NULL value, itsMarc G. Fournier1998-02-05
| | | | | | output at least doesn't appear that its missing something. wasn't particularly confident with removing 'caller' altogether :(
* Fix up this so that it also doesn't use a caller variable...Marc G. Fournier1998-02-05
|
* Inline fastgetattr and others so data access does not use functionBruce Momjian1998-01-31
| | | | calls.
* Add Var.varlevelup to code. More parser cleanup.Bruce Momjian1998-01-20
|
* Parser cleanup.Bruce Momjian1998-01-20
| | | | Add lock to i386 asm.
* Create SubLink nodes in parser for Vadim.Bruce Momjian1998-01-19
|
* Creates the SubLink structure, and the Query->hasSubLink field,Bruce Momjian1998-01-17
| | | | | | | | with supporting code. Creates SubLink node in gram.y. psql.c patch for newatttypmod field.
* New pg_attribute.atttypmod for type-specific information likeBruce Momjian1998-01-16
| | | | | | | | | | | varchar length. Cleans up code so attlen is always length. Removed varchar() hack added earlier. Will fix bug in selecting varchar() fields, and varchar() can be variable length.
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-05 07:28:19 +0000