| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: insert order question |
| Date: | 2011-05-12 20:05:32 |
| Message-ID: | 5730.1305230732@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> writes:
> Does...
> insert into mytbl (col1) values ('a'),('b'),('c');
> ... insert records 'a','b','c' in that order while...
> insert into mytbl (col1) values ('c'),('b'),('a');
> ... insert the records in the opposite order?
I believe so, but it seems unwise to hard-wire a dependency on that into
your application, since this is only an implementation artifact and not
anything guaranteed by the standard. If you need the inserts to occur
in a specific order, issue them as separate commands ... you're not
going to save all that much by having them be one command.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James B. Byrne | 2011-05-12 20:06:06 | Re: How to handle bogus nulls from ActiveRecord |
| Previous Message | David Johnston | 2011-05-12 20:02:24 | Re: insert order question |