On 8/12/07, George Vilches <[EMAIL PROTECTED]> wrote: > > How about the patch below? When you create the cursor, if you want > access to "don't run this SQL, just have playback available", just use > connection.cursor(playback_only=True), and if you want to roll the
This is a simple approach that would probably suffice for management.py based problems, but it isn't really practical on a large scale. For example, QuerySets open their own connections, so it won't be easy to pass an argument to an ORM call to enable capture of playback data. The configuration option will need to be a little more generic - i.e., putting the entire backend into a record mode - not just a single cursor call. > Something that I found a little irksome while working on this is that > the DatabaseWrapper class for each backend doesn't inherit from some > logical parent. I know that all the db-specific functionality is Brian Ferring seems to be on top of this one. There's a separate thread now talking about this refactoring. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
