| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "howachen(at)gmail(dot)com" <howachen(at)gmail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pgsql vs mysql |
| Date: | 2006-07-11 18:59:14 |
| Message-ID: | 44B3F502.6010805@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jan Wieck wrote:
> On 7/11/2006 1:08 PM, Scott Marlowe wrote:
>
>> On Tue, 2006-07-11 at 11:04, Jan Wieck wrote:
>>> On 6/30/2006 1:07 PM, Merlin Moncure wrote:
>>>
>>> > * mysql has a few features here and there which are nice...just to
>>> > name a few, flush tables with lock, multiple insert, etc
>>
>>> The multiple insert stuff is not only non-standard, it also
>>> encourages the bad practice of using literal values directly in the
>>> SQL string versus prepared statements with place holders.
>>
>> I thought it was in the SQL 99 standard...
>
> The SQL bible doesn't say SQL99, it says it is a DB2 specific feature.
hmm:
http://troels.arvin.dk/db/rdbms/#insert
says otherwise - or are we talking a different "multiple insert" ?
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-11 19:08:21 | Re: pgsql vs mysql |
| Previous Message | Jan Wieck | 2006-07-11 18:39:04 | Re: pgsql vs mysql |