- 20 3月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 19 3月, 1999 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 18 3月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 16 3月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 14 3月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
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
-
- 07 3月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 23 2月, 1999 1 次提交
-
-
由 Thomas G. Lockhart 提交于
code. Works here, but not completely implemented past this point.
-
- 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 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 08 2月, 1999 2 次提交
- 07 2月, 1999 1 次提交
-
-
由 Tom Lane 提交于
treated as SELECT INTO TEMP TABLE.
-
- 03 2月, 1999 1 次提交
-
-
由 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 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 25 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 23 1月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 22 1月, 1999 1 次提交
-
-
由 Vadim B. Mikheev 提交于
-
- 21 1月, 1999 1 次提交
-
-
由 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 提交于
-
- 31 12月, 1998 1 次提交
-
-
由 Jan Wieck 提交于
and aggregates. Jan
-
- 18 12月, 1998 1 次提交
-
-
由 Vadim B. Mikheev 提交于
LOCK TABLE IN ... MODE ...implemented
-
- 13 12月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
destructions in 6.4 source using purify. (1) parser/gram.y:fmtId() It writes n+3 bytes into n+1 byte-long memory area if mixed case or non-ascii identifiers given. (2) catalog/index.c: ATTRIBUTE_TUPLE_SIZE bytes are allocated but sizeof(FormData_pg_attribute) bytes are written. Note that ATTRIBUTE_TUPLE_SIZE is smaller than sizeof(FormData_pg_attribute). (for example, on solaris 2.6, Tatsuo Ishii
-
- 04 12月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 14 10月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
timestamp had become a token a while ago, but had been omitted from the keywords.c until recently. This uncovered the omission in the ColId decl.
-
- 09 10月, 1998 2 次提交
-
-
由 Thomas G. Lockhart 提交于
-
由 Bruce Momjian 提交于
-
- 03 10月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
parameters. With it applied a function like CREATE FUNCTION getname(oid8, int4) RETURNS name AS 'SELECT typname FROM pg_type WHERE oid = $1[$2]' LANGUAGE 'sql'; is possible. Mainly I need this to enable array references in expressions for PL/pgSQL. Complete regression test ran O.K. Jan
-
- 30 9月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
Add "timestamp" to list of tokens in keywords.c. Before, TIMESTAMP WITH TIME ZONE did not actually parser. Reorder token lists to be more alphabetical. Remove ARCHIVE keyword which was deprecated in v6.3.
-
- 25 9月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
Remove _all_ PARSEDEBUG print statements.
-
- 16 9月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
Change DEFAULT NULL to send back a NULL pointer rather than a string "NULL". This seems to work, where sending the string led to type conversion problems (and probably the wrong thing anyway).
-
- 13 9月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
Adds a few new keywords, but all are allowed as column names etc.
-
- 02 9月, 1998 1 次提交
-
-
由 Thomas G. Lockhart 提交于
-
- 01 9月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 26 8月, 1998 1 次提交
-
-
由 Bruce Momjian 提交于
-