On Saturday 13 November 2010, you wrote: > @xrg > thanks for clarifiying this (a bit) > > what I was trying to say that after updating a module (changes in py files > as Jay put it) the server has to be restarted. this can only be done > (AFAIK) from someone who has access to the server. Hence importing and > updateing modules using a client updates only the XML in the database, but > does not restart the server - leaving the whole thing in an inconsitent > state by default. I can't believe that this can be considered as > userfriendly. IMHO automatically restarting the server after update and/or > a message telling to do so and/or a button - "restart server" would be > helpful
There are pros and cons to that. Indeed, the fact that the openerp-server process doesn't restart or even reload its modules (as in pythonic files) is sometimes annoying. But, if you look at the "reload()" builtin command of Python, it would /only/ ensure you to reload single module files, excluding object instances that already are in use. So far, it looks just hard to me to build such a complex framework that would hot-replace its ORM instances. Does it worth it? One trick I do all the time is that I mark my changed modules "to upgrade", and then /not/ click the "apply selected changes" button. Instead, I just restart the server . It will apply the changes after having the latest python code. Developers should bear to that. Keep in mind that we are in a heavy-changes period. In production systems, code wouldn't be upgraded that often and should always happen at a 'scheduled maintenance' session. And, on a parallel note, I have recently enhanced the base_quality_interrogation script to take care of all these repetitive steps (eg. server startup, module install/uninstall, tests) that we developers need to do all the time.. -- Say NO to spam and viruses. Stop using Microsoft Windows! -- "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
