One nice thing is that it ships with the binaries for several platforms included and takes care of all the native library loading. BTW, please correct me if anything above is wrong - I'm still new to SQLite. With other RDBMSes, you sometimes have to tune these things for complex workloads, but you probably don't have to deal with them at this level. Unless you do one of these two things, the query planner never will have index stats available. The alternative to running "analyze" periodically is to invoke "pragma optimize" before closing connections, another thing to hand-roll. Incremental vacuum, although likely safer in this regard, only gets rid of entirely empty pages and doesn't compact sparsely used ones. Invoking "vacuum" periodically in a running system could cause application errors because it obtains a global lock for at least some portion of the time it's running. Unless you invoke some form of vacuuming manually, the SQLite file will never decrease in size and likely will grow larger over time. But, with SQLite, you have to think about them, understand them, and add code to make them happen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |