On 2013-10-04 09:01, Paul J Stevens wrote:
On 10/03/2013 08:59 AM, Thomas Raschbacher wrote:
Apart from the mysql issue you mentioned.
Would it not be a good compromise to do something like this instead of
every row seperately?:
BEGIN;
DELETE FROM table WHERE table.id in (SELECT ... LIMIT 100);
COMMIT;
isn't that what I just said?
I just added the LIMIT there
that way it is not that many queries and also doesn'T put long write
locks - the 100 is just an example but I assume you get what I mean ;)
not sure how you'd go about the mysql problem though without a stored
procedure, or temporary table / view maybe?
If not for mysql, that would have been the way to go a long time ago.
Temporary tables might work, but view definitely not: mysql doesn't
really support updateable views.
ok tbh I haven'T used mysql since my early php days back in 2001 .. been
a big fan of postgres for years now ;)
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
