openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #06532
Re: Draft Proposal for a new field type for OpenERP/Odoo
-
To:
Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx>
-
From:
Davide Corio <davide.corio@xxxxxxxx>
-
Date:
Mon, 14 Jul 2014 08:31:31 +0000
-
Accept-language:
it-IT, en-US
-
Cc:
OpenERP Community <openerp-community@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAM10X1=XCeQDdE-sim_aUBDrHwOBWNDJjK5fZoq9ZgY=VtZ1LA@mail.gmail.com>
-
Thread-index:
AQHPnzplM4tehqql402r1vZ9PJlUo5ufGY6AgAACfIA=
-
Thread-topic:
[Openerp-community] Draft Proposal for a new field type for OpenERP/Odoo
On 14 Jul 2014, at 10:22, Guewen Baconnier <guewen.baconnier@xxxxxxxxxxxxxx> wrote:
>
> That's exactly for what the fields.serialised and fields.sparse are meant for.
oh, you’re right.
class serialized(_column):
""" A field able to store an arbitrary python data structure.
Note: only plain components allowed.
"""
--
Davide Corio
davide.corio@xxxxxxxx
ERP Consultant
L.S. Advanced Software Srl
Follow ups
References
