You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As click-odoo-initdb is most useful for development, one good improvement IMHO would be to autodelete the chosen db if existing.
So, if I execute: click-odoo-initdb -rn devel -m web_responsive and devel exists, the script deletes it before re-creating it (maybe from cache, and all that stuff it does).
I think it would lower the barrier for development.
Should it call click-odoo-dropdb behind the scenes? If so, is there an easy or supported way to do it with click without a subprocess?
The text was updated successfully, but these errors were encountered:
As
click-odoo-initdb
is most useful for development, one good improvement IMHO would be to autodelete the chosen db if existing.So, if I execute:
click-odoo-initdb -rn devel -m web_responsive
anddevel
exists, the script deletes it before re-creating it (maybe from cache, and all that stuff it does).I think it would lower the barrier for development.
Should it call
click-odoo-dropdb
behind the scenes? If so, is there an easy or supported way to do it with click without a subprocess?The text was updated successfully, but these errors were encountered: