2009/7/31 Emanuel Calvo Franco :
>> Emanuel Calvo Franco writes:
>>> If we look at page 1994 of the PDF manual of 8.4, the select of the
>>> connectby
>>> function is broken.
>>
>> Uh, I don't understand what you think is broken? The examples all seem
>> to work for me.
>
>
> Sorry for the bad e
> Emanuel Calvo Franco writes:
>> If we look at page 1994 of the PDF manual of 8.4, the select of the connectby
>> function is broken.
>
> Uh, I don't understand what you think is broken? The examples all seem
> to work for me.
Sorry for the bad explanation. I'm talking about the 'style' .
If y
Emanuel Calvo Franco writes:
> If we look at page 1994 of the PDF manual of 8.4, the select of the connectby
> function is broken.
Uh, I don't understand what you think is broken? The examples all seem
to work for me.
regards, tom lane
--
Sent via pgsql-docs mailing li
Hi all,
If we look at page 1994 of the PDF manual of 8.4, the select of the connectby
function is broken.
SELECT * FROM connectby(’connectby_tree’, ’keyid’, ’parent_keyid’,
’pos’, ’row2’, 0, AS t(keyid text, parent_keyid text, level int,
branch text, pos int);
could be formatted like this:
SELE
Magnus Hagander wrote:
On Fri, Jul 31, 2009 at 18:22, Andreas
Wenk wrote:
Hi,
I am wondering why I can't find anything if I use WITH as the search
expression in the online documentation, but get a big result list, if I use
WITH RECURSIVE ...
IMO the resulting list should be the same for both s
On Fri, Jul 31, 2009 at 18:22, Andreas
Wenk wrote:
> Hi,
>
> I am wondering why I can't find anything if I use WITH as the search
> expression in the online documentation, but get a big result list, if I use
> WITH RECURSIVE ...
>
> IMO the resulting list should be the same for both search expressi
Hi,
I am wondering why I can't find anything if I use WITH as the search
expression in the online documentation, but get a big result list, if I
use WITH RECURSIVE ...
IMO the resulting list should be the same for both search expressions.
Andy ideas?
Cheers
Andy
--
Sent via pgsql-docs mai