seeing that use case is really small, I would probably try the simplest approach possible. Something like sandstonedb can make the trick here :)
http://smalltalkhub.com/#!/~gnaritas/SandstoneDb Esteban On 02 Sep 2014, at 14:31, François Stephany <tulipe.mouta...@gmail.com> wrote: > Yep, the binary approach is a bit more fragile and less interoperable. > STON, JSON or XML are all fine with such a small domain I imagine. > > > On Tue, Sep 2, 2014 at 12:31 PM, stepharo <steph...@free.fr> wrote: > > On 2/9/14 09:11, François Stephany wrote: >> If you don't want a separate DB, object serialization with Fuel is an >> option. It's very easy to serialize a graph of objects to disk. >> You can also have a look at SandstoneDB, it's pretty small and some people >> use it. > pay attention that images can get corrupted so I would in addition use a file > based approach (STON or whatever). > >> >> Cheers, >> Francois >> >> >> On Tue, Sep 2, 2014 at 8:17 AM, Roelof Wobben <r.wob...@home.nl> wrote: >> Hello, >> >> I want to try to make a financial app for a organisation. >> >> There are some 50 customers so also 50 invoices a year. >> Then the payments . Also 50 a year. >> >> Cash and bank accounts . Every month some 10 - 20 things. >> >> So on my disk on the programm I now use it costs me some 30 - 50 Kb a year. >> >> What are my options for storage of those data. >> >> I could use a database , but I wonder if there are more and better options. >> >> Roelof >> >> > >
