Hello,
i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1 Is there a chance to make this statement mysql 4.0 compatible or should i update mysql? i want to avoid updating mysql because some old software is running which is not compatible to higher mysql versions.
Thanks, Andre
On Thu, 25 Mar 2010 10:24:37 +0100, Andre Hübner <andre.huebner@gmx.de> articulated:
i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1 Is there a chance to make this statement mysql 4.0 compatible or should i update mysql? i want to avoid updating mysql because some old software is running which is not compatible to higher mysql versions.
In my opinion, continued use of depreciated software is a practice that should be avoided whenever possible. Inevitably, it causes problems as you are now experiencing.
I am somewhat surprised that the older software is not compatible with the newer version of MySQL. Usually, it is the other way around. Have you checked to see if newer versions of the incompatible software exist? I would be willing to wager that they have been updated to accommodate the newer MySQL versions.
-- Jerry Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
There's a fine line between courage and foolishness. Too bad it's not a fence.
Charles Marcus wrote:
In my opinion, continued use of depreciated software
<peeve-mode> It is 'deprecated', not 'depreciated'... </peeve-mode>
Perhaps he's found a way to depreciate free software?
-- Regards, Daryl Tester
Member of the Amalgamated Australian Association Against Apostrophe Abuse. (formerly the 6A's - no, wait ...).
On Thu, 25 Mar 2010 21:52:08 +1030, Daryl Tester <dt-dovecot@handcraftedcomputers.com.au> articulated:
Charles Marcus wrote:
In my opinion, continued use of depreciated software
<peeve-mode> It is 'deprecated', not 'depreciated'... </peeve-mode>
Perhaps he's found a way to depreciate free software?
Cool, now I have the spelling police and a troll on my tail. Perhaps you two could get a room and beef, bellyache, carp, crab, croak, fuss, gripe, grouse, growl, grumble, kick, moan, murmur, mutter, repine, squawk, wail, whine, and or yammer to your heart's content.
By the way, at least I attempted to assist the OP.
-- Jerry Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
Don't make a big deal out of everything; just deal with everything.
On 25.3.2010, at 11.24, Andre Hübner wrote:
i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1
The original code supported dict-sql only if ON DUPLICATE KEY UPDATE was supported by the server. Later I added support for PostgreSQL and SQLite by having them use INSERT triggers that update the data if it already exists. I suppose MySQL 4.0 doesn't support these kind of triggers either?
Writing code manually to first try to UPDATE and if it fails then INSERT would be possible.. But too much trouble for me to spend time on.
Hello,
i use successfully mysql-quotasystem with dovecot 1.2.11 on different servers except for mysql 4.0 servers dovecot internally uses sql: "ON DUPLICATE KEY UPDATE" which was introduced in mysql 4.1
The original code supported dict-sql only if ON DUPLICATE KEY UPDATE was supported by the server. Later I added support for PostgreSQL and SQLite by having them use INSERT triggers that >update the data if it already exists. I suppose MySQL 4.0 doesn't support these kind of triggers either?
Writing code manually to first try to UPDATE and if it fails then INSERT would be possible.. But too much trouble for me to spend time on. its a pity :(
i did now a other way. not really clean... i removed code for ON DUPLICATE KEY UPDATE from C-Code and splitted quota table into two tables. This seems to work because the second insert stays away. not very clean but seems to work...
Thanks, Andre
participants (5)
-
Andre Hübner
-
Charles Marcus
-
Daryl Tester
-
Jerry
-
Timo Sirainen