derez Expert Licensed User Longtime User Jul 23, 2018 #1 an empty b4a app with #AdditionalJar: sqlite-jdbc-3.7.2, with the Jdbcsql library,did not finish compilation. I had to extend the process timeout to 360 and release mode ! the next time it compiled, after the compiler switched from optimized to standard. I can't wait long time for every compilation so I'll probably not use it and stick to the regular connection to b4j handlers. Last edited: Jul 24, 2018
an empty b4a app with #AdditionalJar: sqlite-jdbc-3.7.2, with the Jdbcsql library,did not finish compilation. I had to extend the process timeout to 360 and release mode ! the next time it compiled, after the compiler switched from optimized to standard. I can't wait long time for every compilation so I'll probably not use it and stick to the regular connection to b4j handlers.
Erel B4X founder Staff member Licensed User Longtime User Jul 24, 2018 #2 Why not use the built-in SQLite engine? Upvote 0
derez Expert Licensed User Longtime User Jul 24, 2018 #3 Erel said: Why not use the built-in SQLite engine? Click to expand... I do when the DB is local, I need the b4a app to work on a remote DB. At the moment I have a B4j server that controls the DB with handlers for web access and for b4a access, it works well. I wanted to see how a direct control will work... Upvote 0
Erel said: Why not use the built-in SQLite engine? Click to expand... I do when the DB is local, I need the b4a app to work on a remote DB. At the moment I have a B4j server that controls the DB with handlers for web access and for b4a access, it works well. I wanted to see how a direct control will work...