This wish is for enabling jSQL's locking for alternative SQLite JDBC drivers. Various methods for enabling this could be (this is a repeat found in my post here: https://www.b4x.com/android/forum/t...nd-authentication-support.110565/#post-690205):
1) If in the jSQL library (I'm looking at the source here: https://github.com/AnywhereSoftware/B4J_SQL/blob/master/src/anywheresoftware/b4j/objects/SQL.java)
sqliteLock where public, we could also use JavaObject to set it with a "new ReentrantLock()".
2) Or if there were an "enableSQLiteLock" method in jSQL
3) Or if Initialize2 could just enable the lock if it sees the connection string starting with "jdbc:sqilte"
Then we could have the best of both worlds: 1) Use different SQLite JDBC driver and 2) let jSQL handle the locking as it already does
1) If in the jSQL library (I'm looking at the source here: https://github.com/AnywhereSoftware/B4J_SQL/blob/master/src/anywheresoftware/b4j/objects/SQL.java)
sqliteLock where public, we could also use JavaObject to set it with a "new ReentrantLock()".
2) Or if there were an "enableSQLiteLock" method in jSQL
3) Or if Initialize2 could just enable the lock if it sees the connection string starting with "jdbc:sqilte"
Then we could have the best of both worlds: 1) Use different SQLite JDBC driver and 2) let jSQL handle the locking as it already does
