Recursive Queries
I'm looking into recursive queries and what it would take to support them in
Postgres. Is anyone else looking at this already?
Aside from the Oracle-ish syntax were there other objections to the patch as
posted a while back for 7.3 by Evgen Potemkin?
I have some ideas myself for how to go about this but I'm going to review the
existing patch first. If anyone else has ideas I would like to hear them.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Gregory Stark wrote:
I'm looking into recursive queries and what it would take to support them in
Postgres. Is anyone else looking at this already?
Yes your co-employee Jonah.
http://archives.postgresql.org/pgsql-hackers/2007-01/msg00989.php
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
Gregory Stark wrote:
I'm looking into recursive queries and what it would take to support them in
Postgres. Is anyone else looking at this already?Aside from the Oracle-ish syntax were there other objections to the patch as
posted a while back for 7.3 by Evgen Potemkin?I have some ideas myself for how to go about this but I'm going to review the
existing patch first. If anyone else has ideas I would like to hear them.
My recollection is that the verdict was that it was clode to 100%
unusable - you might want to review the past discussions.
Wasn't somebody else working on this? Jonah? (Maybe you EDB guys need to
talk more ...)
cheers
andrew
Andrew Dunstan wrote:
Gregory Stark wrote:
I'm looking into recursive queries and what it would take to support them in
Postgres. Is anyone else looking at this already?Aside from the Oracle-ish syntax were there other objections to the patch as
posted a while back for 7.3 by Evgen Potemkin?I have some ideas myself for how to go about this but I'm going to review the
existing patch first. If anyone else has ideas I would like to hear them.My recollection is that the verdict was that it was clode to 100%
unusable - you might want to review the past discussions.
Yes, the old patch is unusasble. The change has to be done in a
different part of the code.
Wasn't somebody else working on this? Jonah? (Maybe you EDB guys need to
talk more ...)
He is taking it over for Jonah.
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Bruce Momjian wrote:
Wasn't somebody else working on this? Jonah? (Maybe you EDB guys need to
talk more ...)He is taking it over for Jonah.
Oh, good. That was the piece of missing info. I had a case just
yesterday where this feature would have saved us hours of writing client
code to compute the same thing.
cheers
andrew
The only code that is usable (and performant) is the CONNECT BY patch
made by Evgen Potemkin, It works on production servers on the 8.1.5
I hope that a WITH RECURSIVE will be in the 8.3... but I don't see
anybody working on this... (what a shame...)
Le mercredi 24 janvier 2007 à 17:27 +0000, Gregory Stark a écrit :
I'm looking into recursive queries and what it would take to support them in
Postgres. Is anyone else looking at this already?Aside from the Oracle-ish syntax were there other objections to the patch as
posted a while back for 7.3 by Evgen Potemkin?I have some ideas myself for how to go about this but I'm going to review the
existing patch first. If anyone else has ideas I would like to hear them.
_______________________________________________
Ce message et les �ventuels documents joints peuvent contenir des informations confidentielles.
Au cas o� il ne vous serait pas destin�, nous vous remercions de bien vouloir le supprimer et en aviser imm�diatement l'exp�diteur. Toute utilisation de ce message non conforme � sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.
Les communications sur internet n'�tant pas s�curis�es, l'int�grit� de ce message n'est pas assur�e et la soci�t� �mettrice ne peut �tre tenue pour responsable de son contenu.