Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][OU-ADD] stock_account: nothing to do #3971

Closed

Conversation

hoangtiendung070797
Copy link
Contributor

Nothing to do

@legalsylvain
Copy link
Contributor

legalsylvain commented Jul 1, 2023

/ocabot migration stock_account

@pedrobaeza
Copy link
Member

This one should write cogs in display_type for the journal items that are of this type.

@robinkeunen
Copy link
Contributor

This one should write cogs in display_type for the journal items that are of this type.

@pedrobaeza display_type value is computed in _compute_display_type, do you suggest the code needs to be fixed ? Or is there something to do in this PR ? If so, I'd need some more guidance :-)

@pedrobaeza
Copy link
Member

_compute_display_type is not added in this module, so even if the technique used for filling the value is to launch the compute method, you should relaunch it here for recomputing those that the compute override will impact. Another technique if the compute method is used, is to launch the compute on end migration. But that has several problems:

  • ORM compute methods are slower than SQL queries.
  • They can trigger other dependent computes, so slower and maybe values overwrites that you don't want.
  • If the value computed in the method is needed for any other process, you are deferring its computation, so maybe you obtain errors/wrong data on other places.

Thus, in this case, you should try to do a SQL query that performs that filling in an optimal way and in the adequate moment (pre or post).

@remytms
Copy link
Contributor

remytms commented Feb 8, 2024

Superseeded by this PR

@andreampiovesana
Copy link

close for #4293 ?

@pedrobaeza pedrobaeza closed this Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants