| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Shaun Clements <ShaunC(at)relyant(dot)co(dot)za> |
| Cc: | "'Richard Huxton'" <dev(at)archonet(dot)com>, "'PostgreSQL General'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: : Postgres order by into a RECORD, not ordering |
| Date: | 2005-04-01 16:27:35 |
| Message-ID: | 20050401162735.GA77396@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 01, 2005 at 12:36:53PM +0200, Shaun Clements wrote:
>
> RESOLVED.
>
> It must be a bug in 7.3
Before reaching that conclusion, let's see what you were doing.
> I resolved the problem, by changing the FOR IN statement to FOR IN EXECUTE.
> By changing the Statement into a string, it accommodated for the ORDER BY.
Could you post the code that didn't work and the code that does
work? There might be a better solution than what you did. In any
case, it's good to understand *why* something doesn't work, so if
you post the code then maybe somebody can explain what's wrong.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edmund Bacon | 2005-04-01 16:27:40 | Re: Debugging deadlocks |
| Previous Message | Karl O. Pinc | 2005-04-01 16:19:55 | Best practices for (plpgsql ?) trigger optimization? |