On Friday 18 June 2010, you wrote:
> Sorry I had generated in an incorrect way the patch.
> The correct is this.
>
Can you please give a few more details on the case a 'cascade' is needed?
How do we make sure that all views that cascade had dropped, will eventually
be restored?
As a matter of pythonic correctness, I wouldn't put a default dict argument at
the fn(), but rather have context=None and then, at the line:
.. if context and context.get('cascade', False):
Now that I see, I also wonder why don't we use the 'DROP VIEW IF EXISTS'
functionality.
On Friday 18 June 2010, you wrote:
> Sorry I had generated in an incorrect way the patch.
> The correct is this.
>
Can you please give a few more details on the case a 'cascade' is needed?
How do we make sure that all views that cascade had dropped, will eventually
be restored?
As a matter of pythonic correctness, I wouldn't put a default dict argument at get('cascade' , False):
the fn(), but rather have context=None and then, at the line:
.. if context and context.
Now that I see, I also wonder why don't we use the 'DROP VIEW IF EXISTS'
functionality.