Re: Default order on displaying data without order clause

I think you're confusing my point. You're right that you never want to add an *implicit* default to the order clause. That would be changing the SQL standard which, as you've noted, would be really bad. But, we're talking about a tool that constructs *explicit* queries in order to display the da

Re: Default order on displaying data without order clause

I’m disagreeing with dave. to be clear.you NEVER want to add an implicit default to the order clause. EVER. Postgres returns data in the order that it returns it (sql standard) unless you specify otherwise. the python mantra: it is better to be EXPLICIT than IMPLICIT. If you do not p

Re: Default order on displaying data without order clause

Yeah, but that's just what the spec says about how the SELECT works. It's not a statement about how a user interface should display information. Presenting unordered information is basically guaranteed to be never what the user wants. In this case, the user has to *almost always* edit the query

Re: Default order on displaying data without order clause

Janus schreef op vr 15-03-2019 om 12:20 [+0100]: > In pgAdmin 3, an implicit default order by primary key is used when > displaying data without an otherwise stated order. This is not the > case in pgAdmin 4. The order seems somewhat arbitrary and the > following statement from this site is definit

Default order on displaying data without order clause

In pgAdmin 3, an implicit default order by primary key is used when displaying data without an otherwise stated order. This is not the case in pgAdmin 4. The order seems somewhat arbitrary and the following statement from this site is definit