Skip to content

delete, delete!, and delete_all will make the cache stale #27

sideshowbandana opened this Issue Mar 1, 2012 · 1 comment

2 participants


What do you guys think is the best approach for handling this? How about one of these:

  • do nothing, and tell developers that those operations are dangerous
  • raise if someone were to try to call these methods
  • alias delete to be destroy (but that goes against the docs that delete will just be a straight sql call)
  • some hybrid where a developer can force the delete
  • implement all of the above and let the developer pick :)

Since delete will just be a straight SQL call we should just document that calling delete will by-pass the cache and cause issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.