problem with relational databases is that they do not match really well with object models. nowadays you have a lot of cool solutions that allow you to avoid them (several document-oriented databases, object-oriented, etc.)
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! Esteban On 02 Sep 2014, at 15:18, kilon alios <kilon.al...@gmail.com> wrote: > ah yes thats it , thanks Pierce . It may come handy for my project Ephestos, > though I prefer to keep things inside the Pharo image personally. > > > On Tue, Sep 2, 2014 at 4:04 PM, Pierce Ng <pie...@samadhiweb.com> wrote: > On Tue, Sep 02, 2014 at 03:55:50PM +0300, kilon alios wrote: > > When I was coding in Python for small local databases SQlite was > > recommended , I only have played briefly with it but it looked to me fairly > > easy to use and with a very good performance. But I dont know how well it > > works in Pharo, so maybe someone can jump in and tells us about it . > > Give it a spin: > > http://www.samadhiweb.com/tags/sqlite > http://ss3.gemtalksystems.com/ss/NBSQLite3/ > > Pierce > > >
