Community mailing list archives
Re: Experiences with unusual -u MODULE behaviours?by
David Arnold BA HSG / Gerente
315 304 13 68/ david²elaleman.co
El Alemán S.A.S Office: +57 (1) 651 3766 / Fax: +57 (1) 651 3772
CRA 13 93 40 P4, Bogotá, Colombia
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. El Aleman S.A.S is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
Hi DevelopersI just wanted to ask, if you also sometimes experience very weird behavious in your development workflow. I think -u is supposed to ceep your database consistend with the changes you make in the code?Wired things I could observe, even after the usual mitigation procedures:(Cache clearing, odoo restart, db restart)- Blank page and hanging on a 200 HTTP operation- eternal loop on module loadingThese are very difficult to hunt down, that's probably why they are usually just quietely accepted as being "too complex to solve". (I'm thinkin loud)So I thought a first step would be probably sharing such issues and trying to establish some common patterns out of a collection, because I think this is one of the trickier part of Anthony Lesuisse's developer friendliness...If no one has a better idea, I would propose sharing here all those kind of behaviours, that persistafter:- "odoo.py -u MODULE"-restart- cache clearingbefore:- db restart- server restart- db dump and trying on a fresh db (th point beeing that -u should do this persistance job on the db, right?)Thanks for you opinion, objections, contributions, etc. I'm not even sure, if this is a good idea, but when thinking of "developer friendliness", this is an issue.Regards, David