I'm closing this bug, as it's indeed a very-low priority wishlist that
we can't fix easily, and out of scope at the moment (none of the
proposed solutions are both acceptable and easy to implement)
By low-priority I mean that updating a single module only to a newer
version (with different code) is not something admins should face
routinely on production databases. This is more likely an issue for
test/development environment, and technical people know about this
distinction, and the way the Python interpreter works.
Usually when such an operation occurs in production is because of a
global update of the whole server, and in that case restarting it is
part of the procedure.
Thanks for the suggestion though!
** Changed in: openobject-server
Importance: Undecided => Wishlist
** Changed in: openobject-server
Status: New => Won't Fix
** Changed in: openobject-server
Assignee: RGA(OpenERP) (rga-openerp) => (unassigned)
--
"import module + Apply scheduled upgrades" is not equal to the server command
--update=module_name
https://bugs.launchpad.net/bugs/384826
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: Won't Fix
Bug description:
import module and apply scheduled upgrades transfers the zip file to the server
and installs it "partly" - especially view definitions are not available after
the upgrade.
workaround - use --update=<moduel-name> and restart the server
this is particularly annoying if the module must be installed by a "non expert"
customer who has no access to the server.
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
