From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] >Sent: Tuesday, January 27, 2009 12:04 AM >To: [email protected] >Subject: Re: Cascade delete > > >Victor: have you considered doing this at the db level? I've found that >when done through ON DELETE CASCADE references in postgres these types of >referential deletes are much faster that doing them in ruby (or any >middleware). >
I've thought about it, but AFAIK Sequel (which is my primary DB interface) provides no good means for working with foreighn_keys either (at least, on MySQL, "foreighn_key" column definition just defines INTEGER NOT NULL field). Therefore, I'd be happy to remain on "just Sequel" with all those tasks. In any case "delete all associated also" seems to useful behavior for models. V. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
