In order to share the running transaction into a DAO style data management class, I have wrapped the transaction in an Arc<Mutex> and pass it into the DAO.

The issue is, once the transaction is in there I cannot call commit() on it because it cannot be moved out of the Arc<Mutex> anymore, as the commit requires a mut self.

Any ideas on how to work around this?

  • Cpo@lemm.eeOP
    2·
    1 month ago

    Seems like the into_inner is the way (i see other references to it).

    And yes, transactions should be short-lived, this is just about delegating it to the responsible component.

    • nous@programming.devEnglish
      2·
      1 month ago

      Not sure why you need an arc mutex to delegate it to the responsible component. Seems like the type of thing that should not cross thread boundaries nor be cloned multiple times.

        • BB_C@programming.dev
          5·
          1 month ago

          You appear to be generally confused.

          If you’re using the multi-threaded work-stealing tokio runtime (the default), you are “talking threads”. And if you aren’t, Arc and Mutex would be useless, irregardless of whether you’re doing it right or wrong.