aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/analyze.c
Commit message (Collapse)AuthorAge
* 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.
* 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.
* Change my-function-name-- to my_function_name, and optimizer renames.Bruce Momjian1999-02-13
|
* Added LIMIT/OFFSET functionality including new regression test for it.Jan Wieck1999-02-08
| | | | | | | Removed CURRENT keyword for rule queries and changed rules regression accordingly. CURRENT has beed announced to disappear in v6.5. Jan
* Add TEMP tables/indexes. Add COPY pfree(). Other cleanups.Bruce Momjian1999-02-02
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-01-27
| | | | | | Included patches fix a portability problem of unsetenv() used in 6.4.2 multi-byte support. unsetenv() is only avaliable on FreeBSD and Linux so I decided to replace with putenv().
* SELECT FOR UPDATE is implemented...Vadim B. Mikheev1999-01-25
|
* The following patch finishes primary key support. Previously, whenBruce Momjian1999-01-21
| | | | | | | | | | | | | | | | | | | | a field was labelled as a primary key, the system automatically created a unique index on the field. This patch extends it so that the index has the indisprimary field set. You can pull a list of primary keys with the followiing select. SELECT pg_class.relname, pg_attribute.attname FROM pg_class, pg_attribute, pg_index WHERE pg_class.oid = pg_attribute.attrelid AND pg_class.oid = pg_index.indrelid AND pg_index.indkey[0] = pg_attribute.attnum AND pg_index.indisunique = 't'; There is nothing in this patch that modifies the template database to set the indisprimary attribute for system tables. Should they be changed or should we only be concerned with user tables? D'Arcy
* FOR UPDATE is in parser & rules.Vadim B. Mikheev1999-01-21
|
* 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
* Many more cleanups...Marc G. Fournier1998-12-14
|
* Implement CASE expression.Thomas G. Lockhart1998-12-04
|
* Fix for serial creation.Bruce Momjian1998-10-28
|
* Clean up code in analyze.c for SERIAL data type.Thomas G. Lockhart1998-09-25
| | | | Remove _all_ PARSEDEBUG print statements.
* Support specifying PRIMARY KEY for the SERIAL type.Thomas G. Lockhart1998-09-16
| | | | | Check for a constraint if is_sequence is set and omit making a UNIQUE index if so, since the primary key will cover that for us.
* Allow insert statements to have every columnThomas G. Lockhart1998-09-03
| | | | supplied by a DEFAULT clause. Enables INSERT INTO TABLE DEFAULT VALUES...
* OK, folks, here is the pgindent output.Bruce Momjian1998-09-01
|
* Renaming cleanup, no pgindent yet.Bruce Momjian1998-09-01
|
* Make attalign match type alignment.Bruce Momjian1998-08-26
|
* Fix up crashing symptoms for new serial type by making sure constraintThomas G. Lockhart1998-08-26
| | | | and index name fields are pstrdup'd (copied) rather than reused.
* Support SERIAL column type. Expand column marked is_sequence into threeThomas G. Lockhart1998-08-25
| | | | | | | | | | statements: - the table definition with a default clause referencing the sequence; - a CREATE SEQUENCE statement; - a UNIQUE constraint, which expands into a CREATE INDEX statement. This is not a perfect solution, since the sequence will remain even if the table is dropped. Also, there is no absolute protection on updating the sequence column.
* From: Jan Wieck <jwieck@debis.com>Marc G. Fournier1998-08-18
| | | | | | | | | Hi, as proposed here comes the first patch for the query rewrite system. <for details, see archive dated Mon, 17 Aug 1998>
* makeTargetEntry cleanup.Bruce Momjian1998-07-20
|
* Cleanup makeTargetEntry and remove internal.c.Bruce Momjian1998-07-20
|
* 1) Queries using the having clause on base tables should work wellBruce Momjian1998-07-19
| | | | | | | | | | | | | | | | | | | | | | | | | now. Here some tested features, (examples included in the patch): 1.1) Subselects in the having clause 1.2) Double nested subselects 1.3) Subselects used in the where clause and in the having clause simultaneously 1.4) Union Selects using having 1.5) Indexes on the base relations are used correctly 1.6) Unallowed Queries are prevented (e.g. qualifications in the having clause that belong to the where clause) 1.7) Insert into as select 2) Queries using the having clause on view relations also work but there are some restrictions: 2.1) Create View as Select ... Having ...; using base tables in the select 2.1.1) The Query rewrite system: 2.1.2) Why are only simple queries allowed against a view from 2.1) ? 2.2) Select ... from testview1, testview2, ... having...; 3) Bug in ExecMergeJoin ?? Regards Stefan
* Fix up a couple of comments broken by the automatic indenting process.Thomas G. Lockhart1998-05-29
|
* Add capabilities for automatic type conversion.Thomas G. Lockhart1998-05-09
|
* Small HAVING cleanup.Bruce Momjian1998-03-31
|
* There's a patch attached to fix gcc 2.8.x warnings, except for theBruce Momjian1998-03-30
| | | | | | | | | | | | | | | | | | | | | | | | yyerror ones from bison. It also includes a few 'enhancements' to the C programming style (which are, of course, personal). The other patch removes the compilation of backend/lib/qsort.c, as qsort() is a standard function in stdlib.h and can be used any where else (and it is). It was only used in backend/optimizer/geqo/geqo_pool.c, backend/optimizer/path/predmig.c, and backend/storage/page/bufpage.c > > Some or all of these changes might not be appropriate for v6.3, since we > > are in beta testing and since they do not affect the current functionality. > > For those cases, how about submitting patches based on the final v6.3 > > release? There's more to come. Please review these patches. I ran the regression tests and they only failed where this was expected (random, geo, etc). Cheers, Jeroen
* I started adding the Having Clause and it works quite fine forBruce Momjian1998-03-30
| | | | | | | | | | | | | | | | | | | | | | | | sequential scans! (I think it will also work with hash, index, etc but I did not check it out! I made some High level changes which should work for all access methods, but maybe I'm wrong. Please let me know.) Now it is possible to make queries like: select s.sname, max(p.pid), min(p.pid) from part p, supplier s where s.sid=p.sid group by s.sname having max(pid)=6 and min(pid)=1 or avg(pid)=4; Having does not work yet for queries that contain a subselect statement in the Having clause, I'll try to fix this in the next days. If there are some bugs, please let me know, I'll start to read the mailinglists now! Now here is the patch against the original 6.3 version (no snapshot!!): Stefan
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-26
|
* Pass attypmod through to executor by adding to Var and Resdom.Bruce Momjian1998-02-10
|
* FIx hasSubLinks for Vadim.Bruce Momjian1998-02-06
|
* 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
|
* Remove Query->qry_aggs and qry_numaggs and replace with Query->hasAggs.Bruce Momjian1998-01-15
| | | | | | | | | Pass List* of Aggregs into executor, and create needed array there. No longer need to double-processs Aggregs with second copy in Query. Fix crash when doing: select sum(x+1) from test where 1 > 0;
* Add UNION, GROUP, DISTINCT to INSERT.Bruce Momjian1998-01-11
|
* Bye CursorStmt, now use SelectStmt.Bruce Momjian1998-01-10
|
* Remove old quel labels.Bruce Momjian1998-01-09
|
* Change elog(WARN) to elog(ERROR) and elog(ABORT).Bruce Momjian1998-01-05
|
* Change some mallocs to palloc.Bruce Momjian1997-12-29
|
* Fix for ORDER BY in UNION.Bruce Momjian1997-12-29
|
* Cleanup of UNION ALL fix. Manual page updates.Bruce Momjian1997-12-29
|
* UNION work for UNION ALL and other union stuff.Bruce Momjian1997-12-27
|
* Implementation of UNIONs.Bruce Momjian1997-12-24
|
* Change variable name reference from selectClause to more appropriate ↵Thomas G. Lockhart1997-12-23
| | | | | | | unionClause. Add a few lines of test code playing with the unique flag for unions. Does not do much helpful yet.
* Improve (well, ok, fix) generated constraint name for column CHECK clause.Thomas G. Lockhart1997-12-16
|
* Add information message about implicitly created indices.Thomas G. Lockhart1997-12-09
| | | | Check for duplicate implicit index names and generate unique names.
* Add SQL92-compliant syntax for constraints.Thomas G. Lockhart1997-12-04
| | | | Implement PRIMARY KEY and UNIQUE clauses using indices.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-15 01:47:50 +0000