Skip to content

Master changes to fields.Binary return type #563

@andg-odoo

Description

@andg-odoo

Describe the bug
In:

PythonArchEvalFileHook {odoo_entry: true,
trees: vec![(Sy!("0.0"), Sy!("18.1"), (vec![Sy!("odoo"), Sy!("fields")], vec![Sy!("Binary")])),
(Sy!("18.1"), Sy!("999.0"), (vec![Sy!("odoo"), Sy!("orm"), Sy!("fields_binary")], vec![Sy!("Binary")]))],
if_exist_only: true,
func: |odoo: &mut SessionInfo, entry: &Rc<RefCell<EntryPoint>>, _file_symbol: Rc<RefCell<Symbol>>, symbol: Rc<RefCell<Symbol>>| {
PythonArchEvalHooks::_update_get_eval(odoo.sync_odoo, entry, symbol.clone(), (vec![Sy!("builtins")], vec![Sy!("bytes")]));
PythonArchEvalHooks::_update_field_init(symbol.clone(), None);
}},

fields.Binary returns a datatype of the python bytes.

But since odoo/odoo#244421 fields.Binary in saas-19.3+ now returns a new class (BinaryValue) created for lazy access.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions