I came across this as well and quickly realized that the 'delete' method
should be for confirmation.
On a side note, your subject read as if you were yelling and you should
realize that merb is 100% free and b/c of this you should expect a hiccup
here and there on the way to your goal.
Michael
On Thu, Nov 20, 2008 at 7:13 PM, David Lee <[EMAIL PROTECTED]> wrote:
>
> You should understand the intention of separating delete and destroy.
>
> The analogy is: delete is to destroy what edit is to update. You can
> completely ignore delete and use destroy if you don't like the idea of
> having a separate "Will you delete this?" page, but make sure not to
> confuse the two.
>
> If you want to conform to REST, you should not delete from the DB via
> a GET request anyway.
>
> If you don't care about REST, however, you can just do this in your
> controller:
>
> def delete(id)
> Model.find(id).destroy
> "You destroyed Model #{id}"
> end
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
