There is a chapter in the Enterprise Pharo book on STON that may be of some 
help to you
https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessfulBuild/artifact/book-result/STON/STON.html

The book also talks about other storage mechanisms, see 
http://files.pharo.org/books/enterprise-pharo/ 

HTH,

--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please 
see http://emailcharter.org <http://emailcharter.org/> .

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD and RyCh labs  -  Computer Science Department (DCC)  -  University of 
Chile

> On 02 Nov 2016, at 14:27, sergio ruiz <sergio....@gmail.com> wrote:
> 
> Looks like I might stick with STON.. I am not really worried too much about 
> execution time or anything..
> 
> Need to look at one more thing..
> 
> If a user has say.. many stations.. meaning that they have an 
> OrderedCollection of Stations.. I need to check how that gets serialized, and 
> what happens when it gets pulled back in..
> 
> I will play with it this afternoon..
> 
> Thanks!
> 
> 
> On November 2, 2016 at 12:24:48 PM, p...@highoctane.be 
> <mailto:p...@highoctane.be> (p...@highoctane.be <mailto:p...@highoctane.be>) 
> wrote:
> 
>> Fuel is another option , though ston will be more readable because ston is 
>> text fluel is binary . SQLite is another one . You actually have a ton of 
>> options here. You can even make your own binary or text format if want , 
>> it's easy.
> ----
> peace,
> sergio
> photographer, journalist, visionary
> 
> Public Key: http://bit.ly/29z9fG0 <http://bit.ly/29z9fG0>
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.Village-Buzz.com <http://www.village-buzz.com/>
> http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/>
> http://www.coffee-black.com <http://www.coffee-black.com/>
> http://www.painlessfrugality.com <http://www.painlessfrugality.com/>
> http://www.twitter.com/sergio_101 <http://www.twitter.com/sergio_101>
> http://www.facebook.com/sergio101 <http://www.facebook.com/sergio101>

Reply via email to