| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Marc-André Goderre <magoderre(at)cgq(dot)qc(dot)ca> |
| Cc: | "'pgsql-general(at)postgresql(dot)org' (pgsql-general(at)postgresql(dot)org)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using array_agg in pgr_kdisjkstrpath() error |
| Date: | 2015-04-11 04:43:11 |
| Message-ID: | CAKFQuwbAUy3fv_c5kR93qOJNVj0XQmE3P_RUqk_jDAcygonv8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, April 9, 2015, Marc-André Goderre <magoderre(at)cgq(dot)qc(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sameer Kumar | 2015-04-11 05:59:55 | Re: Limiting user from changing its own attributes |
| Previous Message | Adrian Klaver | 2015-04-10 23:21:01 | Re: no pg_hba.conf entry for replication connection from host |