DeadLock when call save in thread and transaction at the same time.

DBFlow Version: 4.0.3 Description: Simple way to reproduce the problem like this:

  private void testDeadLock() {
          final SimpleModule module = new SimpleModule();
          module.name = "module1";
          module.time = System.currentTimeMillis();
          module.save();

          Thread thread = new Thread(new Runnable() {
              @Override
              public void run() {
                  Log.d(TAG, "save start");
                  module.time = System.currentTimeMillis();
                  module.save();
                  Log.d(TAG, "save finish");
              }
          });
          thread.start();
          FlowManager.getDatabase(SimpleDataBase.class).executeTransaction(new ITransaction() {
              @Override
              public void execute(DatabaseWrapper databaseWrapper) {
                  Log.d(TAG, "save in transaction start");
                  module.time = System.currentTimeMillis();
                  module.save();
                  Log.d(TAG, "save in transaction finish");
              }
          });
      }

Then

07-11 10:35:25.458 4410-4494/? D/MainActivity: save start
07-11 10:35:25.459 4410-4410/? D/MainActivity: save in transaction start
07-11 10:35:55.473 4410-4494/com.example.myapplication W/SQLiteConnectionPool: The connection pool for database '/data/user/0/com.example.myapplication/databases/simple.db' has been unable to grant a connection to thread 2331 (Thread-2) with flags 0x1 for 30.000002 seconds.
                                                                                     Connections: 0 active, 1 idle, 0 available.
07-11 10:36:25.474 4410-4494/com.example.myapplication W/SQLiteConnectionPool: The connection pool for database '/data/user/0/com.example.myapplication/databases/simple.db' has been unable to grant a connection to thread 2331 (Thread-2) with flags 0x1 for 60.001003 seconds.
                                                                                     Connections: 0 active, 1 idle, 0 available.

[agrosner]

same thing. transaction more advantageous because you can do more within a transaction and itll overall be more efficient. Like for example:

list.forEach { it.async().save() }

Will create a transaction for each object and execute them in parallel.

FlowManager.getDatabase(MyDatabase::class.java).beginTransactionAsync { db ->
  list.forEach { it.save(db) }
}.build().execute()

which will do only one transaction for any number of models.

[olbb]

thanks