![]() ![]() The other issue is that SQLite can’t handle concurrent connections (since it’s file based), so you can only have one connection at a time. If this were to happen then you would lost your database. These hosting providers don’t have persistent storage and your app could be restarted at any time. First off, where are you going to host your app? If you’re planning to use something like Heroku or Vapor Cloud, then you’re going to be out of luck. Honestly, my life would be much easier (and cheaper) if I could use SQLite instead of MySQL or PostgreSQL for my app… My question: does it mean that we shouldn’t use SQLite in a production app? Even in an easy scenario like the one I’m describing? It is, however, a good database for both testing and prototyping applications.” This also means it can’t be used across servers. It relies on file locks to maintain database integrity, so it’s not suitable for write-intensive applications. It is designed to be embedded into an application and is useful for single-process applications such as iOS applications. In the book we can read the following: “SQLite is a simple, file-based relational database system. I plan to cache the results, again, in SQLite database if possible. However, several thousands users will use it. It will create its own data and will store it, ideally, in an SQLite database. This server won’t have write operations from the outside. ![]() I’m trying to implement a small server for an iOS app that I have. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |