c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <595716@xxxxxxxxxxxxxxxxxx>]

Hello Nhomar,

Let's keep this improvement in mind for post-v6, I think we will need to
implement a better mechanism for managing things like views and custom
indexes etc. to avoid hand-coding it all in SQL, and this could be part
of it.

I'm removing the milestone because we cannot consider changing this in
5.0 either (stable=only bugfixes)

Thanks for the suggestion, examples and the explanation of your use
cases! :-)

** Changed in: openobject-server
    Milestone: 5.0.12 => None

** Changed in: openobject-server
   Importance: Medium => Wishlist

** Changed in: openobject-server
       Status: In Progress => Confirmed

** Changed in: openobject-server
    Milestone: None => 5.0.12

** Summary changed:

- drop_view_if_exists Dont allow Drop on cascade
+ drop_view_if_exists could allow cascading

** Changed in: openobject-server
    Milestone: 5.0.12 => None

** Changed in: openobject-server
    Milestone: None => 5.0.12

** Changed in: openobject-server
     Assignee: (unassigned) => OpenERP's Framework R&D (openerp-dev-framework)

-- 
drop_view_if_exists could allow cascading
https://bugs.launchpad.net/bugs/595716
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Confirmed

Bug description:
In the method 

drop_view_if_exists

Is not Considered  the cascade option.