On Tue, Sep 02, 2014 at 03:23:41PM +0200, Esteban Lorenzano wrote: > so unless you are really constrained for some reason (like imposition of > customers), or you have real use cases (like doing complex tabular > projections), I would always recommend to take another approach than > relational. > > stay in objects as much as you can!
SQLite is very popular, and the relational model well known enough that a lot of data is available as SQLite database files or easily transformed into them. When dealing with such data, it is nice to be able to work with SQLite data in Smalltalk. Philosophically, I agree with staying in objects as much as possible. However, right now if I am to build a web app with "real world" storage requirements, i.e. *not* on the scale of FB or Google, I'd probably go with PostgreSQL, just by the sheer availability of knowledge and expertise on running a serious PostgreSQL setup. That, or Gemstone. Pierce
