Pierce, Thank you for the answers. Is the wrapper thread safe? I understan the library is thread-safe per se (at least in Android+Java it is), so using the wrapper in Pharo (single-threaded at the OS level) wouldn't cause issues. But I don't know how NativeBoost plays here. Regards! Esteban A. Maringolo 2014-09-25 13:40 GMT-03:00 Pierce Ng <pierce@samadhiweb.com>:
On Wed, Sep 24, 2014 at 01:33:02PM -0300, Esteban A. Maringolo wrote:
How does SQLite scale in terms of table size and so on?
According to https://www.sqlite.org/whentouse.html:
An SQLite database is limited in size to 140 terabytes (2^47 bytes, 128 tibibytes). And even if it could handle larger databases, SQLite stores the entire database in a single disk file and many filesystems limit the maximum size of files to something less than this.
SQLite will normally work fine as the database backend to a website. But if you website is so busy that you are thinking of splitting the database component off onto a separate machine, then you should definitely consider using an enterprise-class client/server database engine instead of SQLite.
I was surprised to know it is based on an old version of PostgreSQL according to this presentation: http://www.pgcon.org/2014/schedule/events/736.en.html
That is a very interesting talk. As it says, SQLite is a replacement for fopen(), not a replacement for PostgreSQL. In the context of my writing tools and applications in Smalltalk, I'd like to enjoy SQLite's robustness, hence my interest in having/building a good Smalltalk wrapper.
Pierce