Re: [HACKERS] SQL99 Hierarchical queries

2005-03-11 Thread Evgen Potemkin
Hi Evgen, How's the syncing with HEAD going? Cheers, Chris I'm working on it. Regards, Evgen. ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [HACKERS] SQL99 Hierarchical queries

2005-03-04 Thread Evgen Potemkin
Hello hackers, Thanks very much for doing this work. Is there some way you can summarize what you did so others can join you in working on it? If it is easier for you to write this in some language other than English, please do, and we'll find translators :) I noticed that the patch

Re: [HACKERS] SQL99 Hierarchical queries

2005-03-01 Thread Evgen Potemkin
Ok, I'm started porting it to 8.0.1 and will fix this also. By the way, did you know any test suit for such queries? To make some regression test. Hello, I can find some examples on internet and prepare regression tests. I think PostgreSQL can support all syntax H.Q. Is more easy created

Re: [HACKERS] SQL99 Hierarchical queries

2005-03-01 Thread Evgen Potemkin
Thanks very much for doing this work. Is there some way you can summarize what you did so others can join you in working on it? If it is easier for you to write this in some language other than English, please do, and we'll find translators :) I noticed that the patch touches the parser,

Re: [HACKERS] SQL99 Hierarchical queries

2005-02-28 Thread Evgen Potemkin
Ok, I'm started porting it to 8.0.1 and will fix this also. By the way, did you know any test suit for such queries? To make some regression test. Regards, Evgen I tested you patch, and it's good work. I would all methods in PostgreSQL. I found query which kill backand WITH t AS ( SELECT

Re: [HACKERS] SQL99 Hierarchical queries

2005-02-24 Thread Evgen Potemkin
I have done initial implementation of SQL99 WITH clause (attached). It's now only for v7.3.4 and haven't a lot of checks and restrictions. What kind of restrictions are on it? Main restriction is that the query inside WITH alias can refer only to back and to itself. For example WITH a as

[HACKERS] Hierarchical queries a la Oracle. for ver 7.3rc1

2002-11-28 Thread Evgen Potemkin
Hi there! Patch itself posted to pgsql-patches. This is a new version of patch i've posted. This for PG version 7.3rc1. Changed syntax, now it's more closer to Oracle's and allows operator other than '='. Removed Const/Var trick, now it's a new FakeVar node used, as a side effect it's not need

Re: [HACKERS] Hirarchical queries a la Oracle. Patch.

2002-11-28 Thread Evgen Potemkin
thanks, it's VERY helpful. understanding SQL99 draft is a bit more difficult than i thought :) regards, --- .evgen On 27 Nov 2002, Hannu Krosing wrote: I attach a railroad diagram of SQL99 WITH RECURSIVE and a diff against mid-summer gram.y which implements half of SQL99 _syntax_ (just the

[HACKERS] Hirarchical queries a la Oracle. Patch.

2002-11-26 Thread Evgen Potemkin
Hi there! Patch is posted to pgsql-patches. docs inside. SQL 99 version will be later. regards, --- .evgen ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] Proposal of hierachical queries (a la Oracle)

2002-11-16 Thread Evgen Potemkin
Ok, full section would be very helpful, i don't have it. --- .evgen On 15 Nov 2002, Rod Taylor wrote: On Thu, 2002-11-14 at 06:52, Evgen Potemkin wrote: Hi there! I want to propose the patch for adding the hierarchical queries posibility. It allows to construct queries a la Oracle

[HACKERS] Proposal of hierachical queries (a la Oracle)

2002-11-15 Thread Evgen Potemkin
Hi there! I want to propose the patch for adding the hierarchical queries posibility. It allows to construct queries a la Oracle for ex: SELECT a,b FROM t CONNECT BY a PRIOR b START WITH cond;B I've seen this type of queries often made by adding a new type, which stores position of row in the

[HACKERS] Proposal of hierarchical queries, a la Oracle

2002-11-15 Thread Evgen Potemkin
Hi there! I want to propose the patch for adding the hierarchical queries posibility. It allows to construct queries a la Oracle for ex: SELECT a,b FROM t CONNECT BY a PRIOR b START WITH cond;B I've seen this type of queries often made by adding a new type, which stores position of row in the