You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a new mash step to an existing recipe, the mash step gets stored in the database but not associated with the mash, so it's disappeared next time you run the program. Culprit is NamedMashEditor::addMashStep() which is directly calling ObjectStoreWrapper::insert() instead of Mash::addMashStep(), plus, MashStep::setMashId() doesn't use the same boilerplate as all the other setters, which means it's not calling down to the ObjectStore/DB layer.
Working on a fix.
The text was updated successfully, but these errors were encountered:
Adding a new mash step to an existing recipe, the mash step gets stored in the database but not associated with the mash, so it's disappeared next time you run the program. Culprit is
NamedMashEditor::addMashStep()
which is directly callingObjectStoreWrapper::insert()
instead ofMash::addMashStep()
, plus,MashStep::setMashId()
doesn't use the same boilerplate as all the other setters, which means it's not calling down to the ObjectStore/DB layer.Working on a fix.
The text was updated successfully, but these errors were encountered: