Postgres Pro
Downloads
Home   >   mailing lists

Re: : Postgres order by into a RECORD, not ordering - Mailing list pgsql-general

From Shaun Clements
Subject Re: : Postgres order by into a RECORD, not ordering
Date
Msg-id 100F78F2B203444BB161BBA7077FF6131CD9DD@srldbexc003.relyant.co.za
Whole thread Raw
List pgsql-general
Tree view
Ignore last email.
must have been delayed.
 
A {FONT-FAMILY: verdana; TEXT-DECORATION: none } A:active {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:link {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:visited {COLOR: #003366; FONT-FAMILY: verdana; TEXT-DECORATION: none } A:hover {COLOR: #ff0000; FONT-FAMILY: verdana; TEXT-DECORATION: underline } .small_text {FONT-SIZE: 9px; COLOR: #003366; FONT-FAMILY: verdana } Kind Regards,
Shaun Clements
-----Original Message-----
From: Shaun Clements [mailto:ShaunC@relyant.co.za]
Sent: 01 April 2005 12:22 PM
To: 'Richard Huxton'
Cc: PostgreSQL General
Subject: Re: : [GENERAL] Postgres order by into a RECORD, not ordering

Hi Again.

I hope you can explain this.
I have a stored procedure which does a query of a table using order by, into a RECORD.
The statement I mentioned earlier, is a FOR  IN.
the data stored into the RECORD, is not ordered by the columns specified, because when I loop through the record, the columns returned in the row are different, to when I manually do a Select query using order by.

I assumed this may have something to do with the index.

Is there any reason why this is so ?

Kind Regards,
Shaun Clements

pgsql-general by date:

Previous
From: Miguel Angel Tribaldos Hervas
Date:
Subject: inherited type
Next
From: Mr Muralidharan Ramakrishnan
Date:
Subject: Tracing Backend process