Hi, It depends… how? which framework do you want to use?
if you use sandstonedb, you can check this old post from Ramon Leon (its author): http://onsmalltalk.com/sandstonedb-simple-activerecord-style-persistence-in-squeak is old, and related to squeak… but it still works :) if you use Voyage (and then MongoDB), you can check the documentation section here: http://smallworks.eu/web/projects/voyage and specially the "Voyage chapter”, from Johan Fabry, here: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/Voyage/Voyage.pier.html finally… if you chose a relational approach, there are several ways to do it, but you could use Glorp and PostgreSQL, and then you can take the article Sven released yesterday as an example )it just came out from the oven): https://medium.com/@svenvc/reddit-st-in-10-cool-pharo-classes-1b5327ca0740 sadly, for sqlite I cannot help you, but someone from this list will have some tips, for sure :) cheers, Esteban ps: btw… a common mistake from people coming to pharo for the first time is to carry with them the way of thinking of other environments. For example, to take a decision of which persistence storage use before having clear the design and demands of the applications. I would postpone that decision until you have a clear view of your needs. I usually do that by using Voyage-Memory (a set of voyage that allows you to keep the data in a singleton, but in an ordered way), and then, when I know how my app will behave, I decide what to use :) On 02 Sep 2014, at 16:32, Roelof Wobben <r.wob...@home.nl> wrote: > Hello Estaban. > > Do you have a tutorial or a example how I can store my data in objects. > > Roelof > > > Esteban Lorenzano schreef op 2-9-2014 15:23: >> 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 >>> >>> >>> >> >
