On Fri, Sep 17, 2010 at 4:32 PM, Michael Glaesemann
wrote:
> This isn't valid syntax: I believe you issued UPDATE users
Woops. I did use the UPDATE and not ALTER command.
On Fri, Sep 17, 2010 at 4:39 PM, Richard Broersma
wrote:
> On Fri, Sep 17, 2010 at 1:32 PM, Michael Glaesemann
> wrote:
On Fri, Sep 17, 2010 at 1:32 PM, Michael Glaesemann
wrote:
> Postgres (nor any other SQL RDBMS) does not guarantee row order unless you
> specify it with an ORDER BY clause.
This is true, but some database will maintain a tables clustering.
MS-Access comes to mind. I don't know if MySQL does t
On Sep 17, 2010, at 16:12 , Carlos Mennens wrote:
> I noticed that my database was in order based on my primary key column
> called 'id' which when from 1 (first) to 6 (last). Today I had to edit
> table data which wasn't anything crazy:
>
> team=#ALTER users SET name = 'David' WHERE id = '1';
>
On Fri, Sep 17, 2010 at 4:12 PM, Carlos Mennens
wrote:
> Thanks for any assistance or clarification.
>
Rows in SQL are unordered. If you want an ordering, specify one on your SELECT.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
htt
I noticed that my database was in order based on my primary key column
called 'id' which when from 1 (first) to 6 (last). Today I had to edit
table data which wasn't anything crazy:
team=#ALTER users SET name = 'David' WHERE id = '1';
UPDATE 1
Now when I do a 'SELECT * FROM users' command in Post
