- 18 1月, 1999 11 次提交
-
-
由 Bruce Momjian 提交于
-
由 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
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
it fails to compile on any machine without a <features.h> header. If this header is actually necessary on Windows, perhaps an #if test is in order.
-
由 Tom Lane 提交于
when a notify is installed.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
per Massimo Dal Zotto.
-
- 17 1月, 1999 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
file containing the latest version of the JDBC driver, allowing it to be compiled and used under JDK 1.2 and later. NB: None (well almost none) of the new methods actually do anything. This release only handles getting it to compile and run. Now this is done, I'll start working on implementing the new stuff. Now this tar file replaces everything under src/interfaces/jdbc. I had to do it this way, rather than diffs, because most of the classes under the postgresql subdirectory have moved to a new directory under that one, to enable the support of the two JDBC standards. Here's a list of files in the tar file. Any file not listed here (in the postgresql directory) will have to be deleted, otherwise it could cause the driver to fail: Peter Mount
-
由 Tom Lane 提交于
report kernel's errno value.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
separately from snprintf() --- HPUX, for one, has snprintf but not vsnprintf. Fix a minor typo in snprintf.c, too.
-
由 Tom Lane 提交于
seem to be portable (HPUX doesn't like it, anyway). Also, clean up StreamConnection(), which was mis-coded to assume that the address family field is already set when it's called.
-
由 Tom Lane 提交于
to ensure that config.h is included as well.
-
由 Tom Lane 提交于
out-of-sync routine prototypes ... the system doesn't compile without this ...
-
由 Tom Lane 提交于
quite as unused as I thought ... how embarrassing.
-
- 12 1月, 1999 1 次提交
-
-
由 Marc G. Fournier 提交于
From: Magnus Hagander <mha@sollentuna.net> Here's another patch for the libpq backend areas. This patch removes all usage of "FILE *" on the communications channel. It also cleans up the comments and headers in the pqcomm.c file - a lot of things were either missing or incorrect. Finally, it removes a couple of unused functions (leftovers from the time of shared code between the libpq backend and frontend).
-
- 11 1月, 1999 3 次提交
-
-
由 Marc G. Fournier 提交于
From: Magnus Hagander <mha@sollentuna.net> Here is a first patch to cleanup the backend side of libpq. This patch removes all external dependencies on the "Pfin" and "Pfout" that are declared in pqcomm.h. These variables are also changed to "static" to make sure. Almost all the change is in the handler of the "copy" command - most other areas of the backend already used the correct functions. This change will make the way for cleanup of the internal stuff there - now that all the functions accessing the file descriptors are confined to a single directory.
-
由 Thomas G. Lockhart 提交于
when deciding whether a field is a year field. Assume *anything* longer than 2 digits (if it isn't a special-case doy) is a valid year. This should fix the "Y1K" and "Y10K" problems pointed out by Massimo recently. Check usage of BC to require a positive-valued year; before just used it to flip the sign of the year without checking. This led to problems near year zero. Allow a 5 digit "concatenated date" of 2 digit year plus day of year. Do 2->4 digit year correction for 6 and 5 digit "concatenated dates". Somehow forgot this originally. Guess not many folks use it...
-
由 Thomas G. Lockhart 提交于
I think NAN is already guaranteed to be there from Jan's work on NUMERIC, but perhaps HUGE_VAL needs some #ifndef's in the same place. Should also include "-Infinity" as -HUGE_VAL sometime; not there yet.
-
- 09 1月, 1999 1 次提交
-
-
由 Byron Nikolaidis 提交于
-
- 08 1月, 1999 1 次提交
-
-
由 Bruce Momjian 提交于
subscriptions yet. It's just a small patch to ecpg to keep it in sync with gram.y. Michael
-
- 07 1月, 1999 9 次提交
-
-
由 Thomas G. Lockhart 提交于
which was not built last time these things changed.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
Use a <citetitle> rather than <xref> when referring to libpq since that chapter is not included in the tutorial.
-
由 Thomas G. Lockhart 提交于
which are not used here.
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
From Magnus Hagander <mha@sollentuna.net>.
-
由 Byron Nikolaidis 提交于
-
- 05 1月, 1999 4 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Jan Wieck 提交于
Anything else is CPU overkill. Jan
-
由 Jan Wieck 提交于
overflow error on high precision calculations where temporary huge precision is required. Jan
-
由 Byron Nikolaidis 提交于
-