Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm calling memc_delete from a MySQL trigger's code. The call is inside a loop. Logging the results, I see that memc_delete sometimes returns 1 (ok, memcached entry deleted) and sometimes returns 0 (entry is not deleted). I suspect the cause is too many calls in a row. If one call is raised before the previous one ends, it causes an error. Does it make any sense?

If yes, Is there any way to 'enqueue' calls, or set a 'wait until finish' mode?

Anyway, I'm trying to figure out the error's cause. I see here that the C/C++ memcached interface allows to translate the error code into a printable string with memcached_strerror, but an equivalent function callable from SQL doesn't seem to exist

Any ideas?

Thanks in advance

share|improve this question
Is it possible that you have 2 triggers running simultaneously for the same rows? – Phil Aug 29 '12 at 15:38
Mmmm, I don't think so. This trigger is raised after update on one table. I execute 'UPDATE' over this table and then the trigger is executed. That's all. Any the MySQL log doesn't show more activity. – jorgeas80 Aug 29 '12 at 16:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.