Josh Berkus a écrit : <blockquote type="CITE">Mr. Nagy, <p>> Recently, I have upgraded my postgresql server from
7.0.2to 7.1.3. <br />> But, <br />> now, one request which was 'good' before, don't want to work any more <br
/>>now. <p>I'm not sure I understand your question. What do you mean "doesn't <br />work"? Please give a detailed
listof all steps taken, including any <br />error messages received. <p>> Now, if I want that my request works well,
Ihave to remove the order <br />> by <br />> statement. But, of course, it is not ordered any more. <p>Er, by
"request"do you mean "query"? <p>Using an ORDER BY statement as you appear to use it in that query is <br />permitted
andcorrect. I suspect that your problem is located somewhere <br />else. For example, what interface tool are you
usingto send queries to <br />the database? <p>-Josh <p>______AGLIO DATABASE SOLUTIONS___________________________ <br
/> Josh Berkus <br /> Complete information technology josh@agliodbs.com <br
/> and data management solutions (415) 565-7293 <br /> for law firms, small businesses fax 621-2533 <br
/> and non-profit organizations. San Francisco <br /> <br /> </blockquote> Hello Josh BERKUS, <p>Thanks for
youranswer and sorry for my english. It was a query and not a request! Well, the query works well on postgresql 7.0.2
butwhen I upgraded the RDBS to 7.1.3, it did not work any more. The error was : Relation e does not exist. <br />But,
inthe 'order by' statement, I removed the 'e.'. Now, the query works well without any error. It is ordered but I think
itis certainly due to the fact that the table was already ordered on disk. So, I have no more errors but I'm not sure
thatit is completely good. <p>PS : The interface tool that I have used to send queries to the database was psql.
<p>Regards<pre>--
Richard NAGY
Presenceweb</pre>