|
Post by hoho0482 on Apr 21, 2020 10:42:44 GMT
Hello, Edit: Typically after hours - solve it as soon as put up a request for help. Think it is some locking occurring. Whilst all code references the singleton DB Manager, I had left the original scene specific DB managers in place. As the admin says here - echo17.proboards.com/thread/2/faq?page=3&scrollTo=272 - don't ever have two DB Managers open to the same DB.... Are there any known issues when configuring DB Managers in a singleton and referencing them across multiple scenes? I have 3 DB Managers all setup in a singleton, with DontDestroyOnLoad, but see inconsistent behaviour when using this to query in other scenes. As examples: 1) Setup the DB Manager in the singleton, but then don't do anything more with it (i.e. run query) in the singleton itself, I get Disk I/O error when then query that DB in another scene. 2) Setup the DB Manager in the singleton, to bypass the disk I/O error, by queuing the DB in the singleton, now in another scene, run exactly the same query in against the singletons DB manager - no results returned. I've created a small project to recreate, but that works fine. So just wonder if you may have some points as to what is happening here? I reverted my real project to define each DB on each scene that requires it, and that all works as it did. Many Thanks. Bob.
|
|
|
Post by echo17 on Apr 21, 2020 12:54:51 GMT
Thanks for the follow up resolution. SimpleSQL uses the sqlite library that does place a lock on the database file to avoid conflicts. Having only one connection at a time is the only way for now to work with a single database file.
|
|