Also what have been told in the minute 25:25 is not completely true,the order of calling methods in same-level modules is not allways predictable,for exemple : if install module without restart the odoo server,the module will be added the last one in the memory loaded modules (which the order determine is the inverse of calling method order) ,but if we restart the server later,the same-level modules will be ordered basing on alphabitical order,in this scnario we have different execution order of methods in the same database and modules just because we have restared the server ,so the conclusion is that we can not make any assumption in developement when in comes to same-level modules and this is not fixed as it has been mentionned in the minute 25:25
@KnowlegeStream Жыл бұрын
Not a full video, Please upload full video.
@some_name1983 Жыл бұрын
by adding names of speakers you can increase the amount of views distinctly, the community knows whom to follow
@mossaabboudchicha8411 ай бұрын
I think that the implementation of the Order of method call in the case of modules in the same level is rediculous ,this order is so important to understand specially in the case of dividing developement in small modules,in this scenario we have found many of modules in the same level that override the same method,and in the end of the day he told us that the order is determined by the name of the module which is in my opinion a non reflected choice,the name of the module is feature dependent and can't be used as method call-stack orderer!!!