On Thursday, April 26, 2012 10:55:13 AM UTC-7, Rodrigo Rosenfeld Rosas wrote:
> Yes, I know but I don't have any control over any of those APIs (Sequel, > Rails and RSpec). I just know this is a limitation of Sequel that won't > allow me to use transactions in situations I can't handle them using blocks. > > I can't rewrite every single software because they were not intended to > work with the Sequel way of dealing with transactions. > > I hope you understand what I mean. > > I understand what you mean. This isn't a limitation in Sequel. As I've shown, the capability exists. It's a deliberate choice not to provide a public API. Your only real problem is with RSpec, because it doesn't provide something it should. It's not like this issue is unique to Sequel, every block-based API has the same issue. Should every block-based API offer a non-block API just to work around limitations in other software? Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/sequel-talk/-/TCwVpCjTjAMJ. 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.
