- 21 2月, 1999 1 次提交
-
-
由 Marc G. Fournier 提交于
From: Tatsuo Ishii <t-ishii@sra.co.jp> 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.
-
- 14 2月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 09 2月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 08 2月, 1999 5 次提交
-
-
由 Jan Wieck 提交于
Removed CURRENT keyword for rule queries and changed rules regression accordingly. CURRENT has beed announced to disappear in v6.5. Jan
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Jan Wieck 提交于
Jan
-
由 Jan Wieck 提交于
added this syntax to rules regression test so it will show up if someone breaks it again. Jan
-
- 07 2月, 1999 1 次提交
-
-
由 Tom Lane 提交于
treated as SELECT INTO TEMP TABLE.
-
- 04 2月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 03 2月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
I search in the planner for the '\xFF' appending. Finally I found in MakeIndexable() in gram.y Attach a patch which removes the "<=" test in USE_LOCALE, might make some queries a bit slower for us "locale-heads", BUT correct result is more important. regards, -- ----------------- Göran Thyni
-
- 02 2月, 1999 2 次提交
-
-
由 Jan Wieck 提交于
when parsestate in makeRangeTable() already contains an opened p_target_relation. Jan
-
由 Bruce Momjian 提交于
-
- 29 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 27 1月, 1999 2 次提交
-
-
由 Marc G. Fournier 提交于
From: Tatsuo Ishii <t-ishii@sra.co.jp> 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().
-
由 Bruce Momjian 提交于
-
- 25 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 24 1月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 23 1月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 22 1月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
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
-
由 Vadim B. Mikheev 提交于
-
- 21 1月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 18 1月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-
- 05 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 01 1月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 31 12月, 1998 1 次提交
-
-
由 Jan Wieck 提交于
and aggregates. Jan
-
- 23 12月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
are available. Problem reported by David Sauer <davids@iol.cz>. Modify information in resulting error message to indicate both agg name and data type.
-
- 19 12月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 18 12月, 1998 1 次提交
-
-
由 Vadim B. Mikheev 提交于
LOCK TABLE IN ... MODE ...implemented
-
- 15 12月, 1998 1 次提交
-
-
由 Vadim B. Mikheev 提交于
New code for locking buffer' context.
-
- 14 12月, 1998 3 次提交
-
-
由 Marc G. Fournier 提交于
Many more cleanups...
-
由 Marc G. Fournier 提交于
Initial attempt to clean up the code... Switch sprintf() to snprintf() Remove any/all #if 0 -or- #ifdef NOT_USED -or- #ifdef FALSE sections of code
-
由 Thomas G. Lockhart 提交于
Try to label CASE columns for a SELECT if not specified with an AS clause.
-