Unless there is a good reason, create your tables and structure before hand and let the app update those table(s) as needed. Creating tables on the fly is overcomplicating the task.
Creating database for an iOS application
-
24-03-2022 - |
Question
I'm coding an application for iOS. Which approach do you think is better: creating tables (create table foo) and everything at once, or only create the tables when it's necessary (only when the user goes to a certain view that uses that table) ? My prototype is creating tables only when it's needed. I have to decide if I'm doing it right in order to start developing my BETA.
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow