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?
>
> 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.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
