El martes 26 de agosto, Jeremy Evans escribió: > I guess there is a slight inconsistency in that area. Currently if _delete > or _remove keys are given, Sequel only adds the appropriate before/after > save hook depending on when the deletion should happen. I suppose at that > point we could remove the object from the cached array, so future attempts > to load the objects will reflect the fact that the object has been deleted, > even if it hasn't been committed to the database yet. I'll add that to my > todo list.
=8) I have solved in my code with one line. It seems not too much annoying :) Thank you for your great work. -- David -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
