by Sharif Mehedi · in Developers · assigned to Luc Saffre

Summary

Children

Comments

• 11 months, 3 weeks ago by Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) : How to avoid this additional loop? The root reason of this issue is that for each slave table in a detail layout, Lino creates a new virtual database field. And this happens when creating the layout handles, which (before our loop) was done lazily, i.e. in unpredictable order. More precisely it happ...
• 11 months, 3 weeks ago by Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) : Yes, #6453 (django.db.utils.OperationalError: no such table: actors_partnertype) is fixed, and in a certain way it makes sense, but can't we somehow avoid this additional loop? Because the extra startup time is tangible during development.
• 11 months, 3 weeks ago by Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) : The fix for #6404 (Inconsistent dataKey in LightWeightContainer values) has at least two negative side effects: it causes startup to become slower, and #6453 (django.db.utils.OperationalError: no such table: actors_partnertype)
• 1 year ago by Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) : pm demotest says "ValueError: 'disabled_fields' is not in list" in all demo projects that use extjs.
  
• 1 year ago by Luc Saffre in reply to Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) : Fixed. Of course kernel must not call get_handle() for actors with a get_handle_name
• 1 year ago by Luc Saffre about #6404 (Inconsistent dataKey in LightWeightContainer values) (1 reply) : After our double-brain fix this morning we are having an exception during pm prep in the events project: Exception: Tried to get static handle for events.VariableEventsByType (get_handle_name is <bound method VariableEventsByType.get_handle_name of lino_xl.lib.events.models.VariableEventsByType>)
  
• 1 year ago by Sharif Mehedi about #6404 (Inconsistent dataKey in LightWeightContainer values) : I am having hard time with this. Not sure what portion of the code to look at.
• 1 year ago by Sharif Mehedi about #6404 (Inconsistent dataKey in LightWeightContainer values) : The first data elem that should come against the null suffix is coming from Actor.get_data_elem which just checks for the app_label.ActorName in the models dict. Considering this from the point of view of runtime execution, I don't see any problem that may arise from this. We can ignore this behavio...
• 1 year ago by Sharif Mehedi about #6404 (Inconsistent dataKey in LightWeightContainer values) : @luc , this is a regression that we need to talk about.
• 1 year ago by Sharif Mehedi about #6404 (Inconsistent dataKey in LightWeightContainer values) : Created new Ticket #6404 (Inconsistent dataKey in LightWeightContainer values).