Re: Using array_agg in pgr_kdisjkstrpath() error - Mailing list pgsql-general

From David G. Johnston
Subject Re: Using array_agg in pgr_kdisjkstrpath() error
Date
Msg-id CAKFQuwbAUy3fv_c5kR93qOJNVj0XQmE3P_RUqk_jDAcygonv8w@mail.gmail.com
Whole thread Raw
In response to Using array_agg in pgr_kdisjkstrpath() error  (Marc-André Goderre <magoderre@cgq.qc.ca>)
List pgsql-general
On Thursday, April 9, 2015, Marc-André Goderre <magoderre@cgq.qc.ca> wrote:
Hello all,
I hope someone will can help me.

Then, where's the difference between the result of (select array_agg(end_id::integer)::integer[]  as id from n2) AND '{28411,25582}'

There isn't...though technically the former is an integer array and the later is an unknown literal.  It gets implicitly cast, I think, to an int[] so that it can get matched to the only? function with that name.

A self-contained example would likely help...those who are responsible for pgrouting.  The error is coming from the function so debugging it from the inside would help.

Does the order of the integers matter?

David J.

pgsql-general by date:

Previous
From: Marc-André Goderre
Date:
Subject: Using array_agg in pgr_kdisjkstrpath() error
Next
From: Sameer Kumar
Date:
Subject: Re: Limiting user from changing its own attributes