Post by hoho0482 on Oct 7, 2020 16:09:12 GMT
Not a question relating to SimpleSQL itself, but more just after some advice from board members.
My DB is growing as I continue to add content to my app (iOS and Android), and it is clear it will exceed 3MB by the time the app is ready for release (have Vacum(ed)).
The reason for being concerned about a paltry 3MB is it is the largest single file size that can be synced to Google Play Game Services and I want to implement this. App users can edit the data through the app and I need away they can save their efforts off the device.
As such I'm wondering if there is a way to get around this? Could I have one logical file that SQL sees split into several physical files by some means? The app itself is educational, and content is modular, so I could split the DB Manually in 3 or so separate files and handle that in the app - but quite a big rewrite job.
Thanks.
Bob.
My DB is growing as I continue to add content to my app (iOS and Android), and it is clear it will exceed 3MB by the time the app is ready for release (have Vacum(ed)).
The reason for being concerned about a paltry 3MB is it is the largest single file size that can be synced to Google Play Game Services and I want to implement this. App users can edit the data through the app and I need away they can save their efforts off the device.
As such I'm wondering if there is a way to get around this? Could I have one logical file that SQL sees split into several physical files by some means? The app itself is educational, and content is modular, so I could split the DB Manually in 3 or so separate files and handle that in the app - but quite a big rewrite job.
Thanks.
Bob.
