Well we don't want to store any python structure, because this is meant to work for client/user. with no technical background. It would be plain text, it's just metadata.
Why not json? Well because XML is simpler easier, and can allow easy why to manipulate it using web modules to do whatever using xslt. This is made to allow user to add fields but with no impacts to the data structure. That's exactly for what the fields.serialised and fields.sparse are meant for. Where is that information? ALIEN GROUP LDA <http://www.alien-group.com> Alaney Dória CEO [email protected] tm.+244 925 999 331 | +244 913 728 600 Linkedin <http://pt.linkedin.com/pub/alaney-d%C3%B3ria/36/9a7/607/pt> Facebook <https://www.facebook.com/aliengrouplda> Facebook <http://www.linkedin.com/company/alien-group-lda> Código QR Rua Doutor Agostinho Neto, 156, Bairro Azul, Luanda - Angola, Tel: +244 913 728 600 | +244 913 728 650, Website: www.alien-group.com <http://www.alien-group.com>, Email: [email protected] <mailto:[email protected]> Não imprima este email caso não seja estritamente necessário. A Terra agradece-lhe! On 07/14/2014 09:31 AM, Davide Corio wrote: > On 14 Jul 2014, at 10:22, Guewen Baconnier <[email protected]> > 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 > [email protected] > ERP Consultant > L.S. Advanced Software Srl > > > > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
