← Back to team overview

openerp-community team mailing list archive

Re: How are new fields added to the database?

 


+1 to Niels' reply, a perfect tip for a developer!
On Thursday 04 October 2012 10:52 PM, Niels Huylebroeck wrote:

My rule of thumb is:
.py  changed : restart server
.XML changed : update module
__openerp__ changed : update module list, then update module
.po changed : update module then restart server.

On Oct 4, 2012 6:52 PM, "Mario Arias" <the.clone.master@xxxxxxxxx <mailto:the.clone.master@xxxxxxxxx>> wrote:

    In my experience, not sure if I am missing something there....,
    when you upgrade a module from inside the client, not everything
    gets reflected immediately....  mostly that sometimes new fields
    in a view give errors because OpenERP is still using the old
    python code...
    so in the end I have to restart OpenERP to complete the update...

    If there is a way to avoid this, please share...  !!!   :-)

    Regards,
    -Mario

    On Thu, Oct 4, 2012 at 9:38 AM, W. Martin Borgert
    <debacle@xxxxxxxxxx <mailto:debacle@xxxxxxxxxx>> wrote:

        Quoting "Niels Huylebroeck" <nh@xxxxxxxxxx
        <mailto:nh@xxxxxxxxxx>>:

            Update the module that contained said changes, if unsure a
            "base" module
            update will re-do and recheck everything (not always the
            best solution).


        OK, I did an --update=all, which helped, too.

        Are there any disadvantages of upgrading all modules, other than
        startup of the server takes some time?


            2012/10/4 W. Martin Borgert <debacle@xxxxxxxxxx
            <mailto:debacle@xxxxxxxxxx>>

                Hi,

                this is probably a very basic question:

                When I upgrade from one version to another and a model
                gets a new field,
                how is this field added to the database?

                Example: I upgraded from nightly build
                6.2dev-20120928-230101-1 to
                6.2dev-20120930-230101-1. In changeset 4465 between
                the versions, the
                model 'ir.model.access' got a new boolean field
                "active", which is not
                in my database.

                What do I have to do to migrate the database? (In the
                Django world,
                there "south", probably because of the migrating
                swallows...)

                Thanks in advance!




        _______________________________________________
        Mailing list: https://launchpad.net/~openerp-community
        <https://launchpad.net/%7Eopenerp-community>
        Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
        <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
        Unsubscribe : https://launchpad.net/~openerp-community
        <https://launchpad.net/%7Eopenerp-community>
        More help   : https://help.launchpad.net/ListHelp



    _______________________________________________
    Mailing list: https://launchpad.net/~openerp-community
    <https://launchpad.net/%7Eopenerp-community>
    Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
    <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
    Unsubscribe : https://launchpad.net/~openerp-community
    <https://launchpad.net/%7Eopenerp-community>
    More help   : https://help.launchpad.net/ListHelp



_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp


References