[jifty-devel] Jifty-DBI: patch proposal for a delete method for the Collection class

Jesse Vincent jesse at bestpractical.com
Fri Oct 20 12:44:06 EDT 2006

>  Because other agents may then be in charge to propagate those deletions
> to other systems, if the deletions made by the operator are not atomic,
> there may be cases where the user will be removed her accesses for
> a ressource on some systems but kept them on others during a not so
> short time period.
>  If granting accesses to the same ressource on various system may spread
> on a (relatively) long period, it is very important (IMO) that their
> revocation be as quick (and atomic) as possible.

So. _atomic_ is something else entirely. Jifty::DBI has support for SQL
transactions.. That might be another way to get a delete that's atomic
and doesn't violate JDBI abstraction.

>  regards,
>  -F.
> PS: I withdraw my demand to have a delete method at the JDBI::Collection
>     level: parallel to this message writting, I had dig around the code
>     in order to find out how to get a WHERE clause whose columns are not
>     qualified.  Unfortunately that would oblige to modify too much code,
>     and I think I have a workaround that will fit at my application level.
>     Sorry for the buzz.

Discussion is good. Even disagreement is good :) It helps to make
peoples' ideas and intents clearer.

More information about the jifty-devel mailing list