I would love to have a digest of the problems you encountered and the
solution.
Because like that we could write a better documentation.
I cannot because I do not face the problems (since I'm not developing real
apps for lack of time/concentration....).
Stef
On Sat, 04 Mar 2017 12:15:39 +0100, Sabine Manaa <manaa.sab...@gmail.com>
wrote:
Hi Hilaire,
it is interesting to see your posts and having similar topics as me when
starting to use voyage.
I ended up with saving ZTimestamps. But I will think about storing
strings too, because this is more readable when having direct look into
mongo.
There was a discussion in slack a few days ago (February, 21st) about
saving Dates in voyage.
RegardsSabine
2017-03-04 11:21 GMT+01:00 HilaireFernandes [via Smalltalk] <[hidden
email]>:
Concerning this problem, one option I found is to get far away of the
Voyage/Mongo Date/DateAndTime representation/conversion and stick to
string, not really efficience, but well...
mongoBirthday<mongoDescription>^ VOToOneDescription new
attributeName: 'birthday'; accessor: (MAPluggableAccessor
read: [:person | person birthday ifNotNil: [person
birthday yyyymmdd]] write: [:person :string |string
ifNotNil: [person birthday: stringasDate]]); yourself
Le 03/03/2017 à 21:12, Hilaire a écrit :
Not sure it is related to this:
http://forum.world.st/Possible-bug-with-Voyage-Mongo-date-tt4735597.html
--Dr. Geohttp://drgeo.eu
http://drgeo.eu
If you reply to this email, your message will be added to the
discussion below:
http://forum.world.st/Voyage-and-Date-tp4937235p4937262.htmlTo start a
new topic under Pharo Smalltalk Users, email [hidden email]To
unsubscribe from Pharo Smalltalk Users, click here.
NAML
View this message in context: Re: Voyage and Date
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
--
Using Opera's mail client: http://www.opera.com/mail/
