Peristence with SandStone or Voyage -> Bypassing the saving of a variable.
So, I tried using mongo voyage for persistence of my Models, and when trying to the SsStateMachine, Mongo Voyager had problems figuring out what to do with my state machine.. So, it occurred to me.. the state machine really does nothing but guide the order through its journey. By the time the order is complete, the state machine is irrelevant.. and there is no chance that the state machine will ever be relevant.. So, my question is.. Is there any way to mark a variable (like statemachine) as âdo not persistâ? This would solve all my problems.. Thanks! ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101
Hi Sergio, have a look at VOTransientDescription I also have attributes which are not persistent. I define them at class side like this: mongoAccountingRecords <mongoDescription> ^ VOTransientDescription new attributeName: 'accountingRecords'; yourself Regards Sabine 2017-07-13 23:40 GMT+02:00 sergio_101 [via Smalltalk] < ml+s1294792n4954802h57@n4.nabble.com>:
So, I tried using mongo voyage for persistence of my Models, and when trying to the SsStateMachine, Mongo Voyager had problems figuring out what to do with my state machine..
So, it occurred to me.. the state machine really does nothing but guide the order through its journey. By the time the order is complete, the state machine is irrelevant.. and there is no chance that the state machine will ever be relevant..
So, my question is..
Is there any way to mark a variable (like statemachine) as âdo not persistâ?
This would solve all my problems..
Thanks!
---- peace, sergio photographer, journalist, visionary
Public Key: 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.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101
*signature.asc* (852 bytes) Download Attachment <http://forum.world.st/attachment/4954802/0/signature.asc>
------------------------------ If you reply to this email, your message will be added to the discussion below: http://forum.world.st/Peristence-with-SandStone-or- Voyage-Bypassing-the-saving-of-a-variable-tp4954802.html To start a new topic under Pharo Smalltalk Users, email ml+s1294792n1310670h65@n4.nabble.com To unsubscribe from Pharo Smalltalk Users, click here <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&nod...> . NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant...>
-- View this message in context: http://forum.world.st/Peristence-with-SandStone-or-Voyage-Bypassing-the-savi... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Oh! good idea.. iâll take a look.. i ended up throwing them into a temp variable.. then saving.. then bringing it back.. thanks! On July 14, 2017 at 2:20:42 AM, Sabine Manaa (manaa.sabine@gmail.com) wrote: have a look at VOTransientDescription I also have attributes which are not persistent. I define them at class side like this: mongoAccountingRecords     <mongoDescription>     ^ VOTransientDescription new         attributeName: 'accountingRecords';         yourself Regards Sabine ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101
participants (2)
-
Sabine Manaa -
sergio ruiz