Re: [development] MySQL Insert on Duplicate Key Update
Khalid- I assumed so. In theory, database.pgsql.inc could intepret this line, but I also asume that using this syntax isn't a huge performance gain. 'Nuff said. - Kem From: "Khalid B" <kb@2bits.com> Subject: Re: [development] MySQL Insert on Duplicate Key Update To: development@drupal.org Message-ID: <4a9fdc630609060818m410e2f5eve53210f5f1c1287@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed One word: PostgreSQL. On 9/6/06, Ken Rickard <agentrickard@gmail.com> wrote:
All-
What is the opinion regarding the use of MySQL's syntax for:
INSERT .... ON DUPLICATE KEY UPDATE
http://dev.mysql.com/doc/refman/4.1/en/insert-on-duplicate.html
I haven't seen any code that uses it. Is that habit or policy?
- Ken Rickard agentrickard
On 06 Sep 2006, at 22:35, Ken Rickard wrote:
I assumed so. In theory, database.pgsql.inc could intepret this line, but I also asume that using this syntax isn't a huge performance gain.
We stick to ANSI SQL because that is the most portable solution. It makes that Drupal works with both MySQL and PostgreSQL without any hacks. Hopefully, it also means that, in future, we can support databases like Oracle with fewer pains. One day, it might turn out to be really important, but until then, it's just theory, of course. :-) -- Dries Buytaert :: http://www.buytaert.net/
participants (2)
-
Dries Buytaert -
Ken Rickard