Android Question SQL.close

From Activity_Resume start it (start the service -> open the db) and stop the service from Activity _Pause. In the service close the db.

Thank you for your answer. But SQL is initialized from starter service.
As i see at log, odd times entry point is Starter service(does not crash), even times entry point is main activity and after that starts starter service(app crashes because SQL is not initiliazed).
Is there any bug with starter service?

p.s. b4a is latest version

yiankos1 said:

Thank you for your answer. But SQL is initialized from starter service

Click to expand...

Quoting @Erel from the Starter Service Tutorial ... https://www.b4x.com/android/forum/t...sistent-single-entry-point.57599/#post-363053

However you do not need to close SQL. The file handle will be closed automatically when the process is killed.

Click to expand...

No. There is no bug but the starter service is just to start some things. I prefer not to use it. Use another service than the starter service. E.g. I have several services for db handling, encryption, communication, etc.

So start and stop the - let's call it "db service" by your own code. Then you have no side effects and all under control.

Closing the db intentionally is a good practice. Check if it's initialized and if not reopen it.

yiankos1 said:

As i see at log, odd times entry point is Starter service(does not crash), even times entry point is main activity and after that starts starter service(app crashes because SQL is not initiliazed).
Is there any bug with starter service?

Click to expand...

This is unexpected assuming that you are not doing something wrong like starting the starter service yourself.

Please post the logs and if possible post a project that demonstrates it.

KMatle said:

There is no bug but the starter service is just to start some things. I prefer not to use it.

Click to expand...

I consider it a bad suggestion.

KMatle said:

Closing the db intentionally is a good practice.

Click to expand...

I consider it a bad suggestion as well. Especially in the general case.

Android apps are different than desktop apps. They don't have a clear or well defined closing event. You can make your app more complex than it should be by closing the database in Activity_Pause (of each activity) and then open it again. Nothing good will come out of this.

So @mangojack 's reply is correct? Leave SQL "open" and wait for OS to close it?

Yes. Unless your app has an explicit exit point. Most apps don't.