I confirm your query determining the fully expanded list of A_ids works as
I explicitly tried it.
Now. I have actually simplified the problem before presenting it here in
the list. But I just tried to extrapolate the solution back to the
original problem and failed miserably :-(
Yes, that is
null;
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of MM
Sent: Friday, June 15, 2018 2:03 PM
To: SQLite mailing list; ryansmit...@gmail.com
Subject: Re: [sqlite] Recursive query
>
> On 2018/06/15 3:19 PM, MM wrote:
> I hav
>
> On 2018/06/15 3:19 PM, MM wrote:
> I have table A of rows with column "object_id", and 2 NULL columns A_id
> and B_id.
> Each row of A (among rows with the same object_id) either references
> table A itself or table B, ie columns A_id and B_id are mutually
> exclusive.
> e.g.
> Table A
> object
On 2018/06/15 3:19 PM, MM wrote:
I have table A of rows with column "object_id", and 2 NULL columns
A_id and B_id.
Each row of A (among rows with the same object_id) either references
table A itself or table B, ie columns A_id and B_id are mutually
exclusive.
e.g.
Table A
object_id A_id
foo.A_id = A.object_id
inner join B
on A.B_id = B.object_id;
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of MM
Sent: Friday, June 15, 2018 9:19 AM
To: SQLite mailing list
Subject: [sqlite] Recursive query
I have table A of rows with
I have table A of rows with column "object_id", and 2 NULL columns
A_id and B_id.
Each row of A (among rows with the same object_id) either references
table A itself or table B, ie columns A_id and B_id are mutually
exclusive.
e.g.
Table A
object_id A_id B_id
...
1 NULL
On Jan 12, 2014, at 11:02 AM, Darren Duncan wrote:
> I would expect so; you can't have WITH RECURSIVE without WITH.
It’s taking shape:
http://www.sqlite.org/src/timeline?r=common-table-expr&nd
Oh, so, exciting! :)
___
sqlite-users mailing list
sql
On 1/11/2014, 7:33 AM, Petite Abeille wrote:
On Jan 10, 2014, at 4:34 PM, Richard Hipp wrote:
FYI: The sponsor is now indicating that they want to go with WITH
RECURSIVE. So the CONNECT BY branch has been closed and we are starting to
work on a WITH RECURSIVE implementation.
Much excellent
On Jan 10, 2014, at 4:34 PM, Richard Hipp wrote:
> FYI: The sponsor is now indicating that they want to go with WITH
> RECURSIVE. So the CONNECT BY branch has been closed and we are starting to
> work on a WITH RECURSIVE implementation.
Much excellent. And much thanks to such rational sponsor
On 10.01.2014 17:34, Richard Hipp wrote:
On Wed, Jan 8, 2014 at 2:35 PM, Richard Hipp wrote:
FYI: The sponsor is now indicating that they want to go with WITH
RECURSIVE. So the CONNECT BY branch has been closed and we are starting to
work on a WITH RECURSIVE implementation.
Thank you, SQL
> That's great news! This will be a serious step up in feature set for
SQLite, both in ease of use and power, I look forward to it. -- Darren
Duncan
It will be available in the SQLite Gold edition for $10,000. {jk}
___
sqlite-users mailing list
sqlite-u
On 1/10/2014, 7:34 AM, Richard Hipp wrote:
On Wed, Jan 8, 2014 at 2:35 PM, Richard Hipp wrote:
The sponsor might have a big pile of preexisting Oracle10g CONNECT BY code
that they need to run. I feel sure that if they just want "recursive
queries" for use in code that has not yet been written
This is really great news !
Will it be developped also for SQLite 4 ?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Wed, Jan 8, 2014 at 2:35 PM, Richard Hipp wrote:
>
>
> The sponsor might have a big pile of preexisting Oracle10g CONNECT BY code
> that they need to run. I feel sure that if they just want "recursive
> queries" for use in code that has not yet been written then we can convince
> them to go w
On Wed, Jan 8, 2014 at 2:28 PM, Petite Abeille wrote:
> Aha… I see… well… if that mysterious sponsor is familiar with ‘connect by’
> they should have no issue with a recursive ‘with’ clause syntax, which is
> what Oracle provides now.
>
The sponsor might have a big pile of preexisting Oracle10g C
Aha… I see… well… if that mysterious sponsor is familiar with ‘connect by’ they
should have no issue with a recursive ‘with’ clause syntax, which is what
Oracle provides now.
See "Recursive Subquery Factoring” in Oracle’s very own documentation:
http://docs.oracle.com/cd/E11882_01/server.112/e
That branch is a "sponsored" change. We are in communication with the
sponsor asking if they will consider WITH RECURSIVE syntax. Their original
request specified Oracle10g-compatible CONNECT-BY syntax. It depends on
what the sponsor really wants. (We await their reply.)
The code will only mak
Hello,
Couldn’t help but notice a brand new branch in SQLite’s repository, the one
labeled "Start a new experimental branch for support of Oracle-style CONNECT BY
syntax.”.
http://www.sqlite.org/src/info/4365ddd62d
Two reactions:
(1) Recursive queries! Yes! Hurray! :D
(2) CONNECT BY syntax?!
Alexander Yap <[EMAIL PROTECTED]> writes:
>
> Hi All,
> I just want to know if WITH RECURSIVE query is supported by SQLite.
>
> Thanks in advance.
>
> Regards,
>
> Alex
http://www.sqlite.org/lang_select.html
MikeW
___
sqlite-users mailing list
sql
Hi All,
I just want to know if WITH RECURSIVE query is supported by SQLite.
Thanks in advance.
Regards,
Alex
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Hi,
Are you planning on any Recursive Query support in SQLite at any time?
Many DBMS's support this and more are doing so. For me personally it
would help a great deal.
Pasted below is some example explaining the workings of such a query.
Greetings,
Marco.
Example schema: ParentChild(pa
21 matches
Mail list logo