I can save a whole object, and retrieve a whole object with Fuel.
All I need is persistence of new things:
New fencers (or overwriting fencer data)
New fencers (or overwriting fencer data)
Persisting empty pools
Persisting bout scores, as they occur
Persisting completed bouts
Persisting collections of completed bouts.
Persisting collections of completed, part-completed and unstarted bouts.
Persisting bout scores, as they occur
Persisting completed bouts
Persisting collections of completed bouts.
Persisting collections of completed, part-completed and unstarted bouts.
All reference to the data in use will be from within the image.
Being able to retrieve a whole competition, if a server has failed.
Being able to retrieve a whole competition, if a server has failed.
SandstoneDB does not pass it's Test suite in either Pharo 4 or Pharo 5
So Fuel it is. I can store any object to disc with fuel.
Therefore, I can store fencers, the dictionary of all the fencers.
For the future: investigate if Magma (an in-image persist-to-disc object DB would speed things up)
Fuel-SIP
aka Simple Image-based Persistence with Fuel
the instance methods are just what I do with my manual Fuel code, with an extra level of indirection
materializeFrom:
serializeTo:
The class methods seem
Fuel-SIP
aka Simple Image-based Persistence with Fuel
the instance methods are just what I do with my manual Fuel code, with an extra level of indirection
materializeFrom:
serializeTo:
The class methods seem
No comments:
Post a Comment