Raphael Collet

Odoo developer

[Raphael Collet @RaphaelCollet]

@simahawk @reis_pt You are totally right: freezegun is the right tool for freezing dates. The point of the slide was to show an example that is very easy to understand.

[Raphael Collet @RaphaelCollet]

@reis_pt The date is Fabien's birth day, actually ;-)

[Raphael Collet @RaphaelCollet]

@wtaferner From Odoo 12.0 on, related fields are readonly by default https://t.co/sfR1Hq7fet

[Raphael Collet @RaphaelCollet]

@jaynvora So nice: I don't have to tell people the cool stuff I am working on, @jaynvora does it for me!
Thanks for sharing my work :-)

[Raphael Collet @RaphaelCollet]

@jaynvora I have not found this by myself. Thanks @beledouxdenis for finding out where that damn closed cursor was coming from!

[Raphael Collet @RaphaelCollet]

@bouvyd @reis_pt Not everything can be flushed later:
- create() performs INSERTs immediately;
- unlink() performs DELETEs immediately;
- many2many updates are performed immediately (if the relation needs some update).

Actually only updates on table columns can be flushed later.

[Raphael Collet @RaphaelCollet]

@bouvyd @reis_pt Correct, the equivalence with commands is something like:

self.related_ids = rset
is equivalent to
self.write({'related_ids': [(6, 0, rset.ids)]})

self.related_ids |= rset
is equivalent to
self.write({'related_ids': [(4, id) for id in rset.ids]})

[Raphael Collet @RaphaelCollet]

@gurneyalex @Odoo Yes! A modification of a dependency marks all direct and indirect dependent fields to recompute.

[Raphael Collet @RaphaelCollet]

@stefan_opener Note that a computed field may be declared as depending on context values and uid: see decorator depends_context(). In that case, the cache will hold separate values for different context/uid.

[Raphael Collet @RaphaelCollet]

@stefan_opener The cache may hold more values than expected only when you switch users *within* a request with self.with_user(...) or self.sudo().

[Raphael Collet @RaphaelCollet]

@stefan_opener I guess you refer to the "record cache". This cache is *never* shared across requests, as the cached values depend on the current database transaction.

[Raphael Collet @RaphaelCollet]

@CecileTonglet Have a look at gitless. I never used it, but it sounds very interesting.

[Raphael Collet @RaphaelCollet]

@PedroMBaeza @bouvyd In the case of a many2many, if A.subrecords = A1+C1 and B.subrecords = B1+C1, then (A+B).subrecords = A1+C1+B1 (the second occurrence of C1 has been discarded).

[Raphael Collet @RaphaelCollet]

@PedroMBaeza @bouvyd (A+B).subrecords = (A+B).mapped('subrecords'), i.e., (A1+A2) | (B1+B2) (a union of recordsets, returning them in order of first occurrence). So, in the case of a one2many, subrecords are disjoint, and therefore (A+B).subrecords = A1+A2+B1+B2 (in that order).

[Raphael Collet @RaphaelCollet]

@Seb_Beau @odony @rvalyi @PedroMBaeza Maybe this? https://t.co/AZyKHAJOyM

[Raphael Collet @RaphaelCollet]

@sswapnesh But changing that default behavior comes with a nasty migration job...

[Raphael Collet @RaphaelCollet]

@sswapnesh I agree with you. This is not my design.

[Raphael Collet @RaphaelCollet]

@moylop260 @legalsylvain @rafaodoo @OdooCommunity @Vauxoo @Odoo And by the way, thanks for pointing out the bug with the fix!

[Odoo @Odoo]

How did we optimized the creation of records in #Odoo 12.0 by Raphael Collet at #OdooExperience
https://t.co/FK9idelgDu