Based on the Paul suggestion, one can write a description to get
DateAndTime right.
Hopefully this could be fixed in Voyage
Hilarie
mongoAccesstime
^ VOToOneDescription new
attributeName: 'accessTime';
accessor: (MAPluggableAccessor
read: [:userClient| userClient
Thanks for the idea.
For me it is a bug[2], like the other one related to Date persistency,
saved as DateAndTime, then shifting you one day[1].
Hilaire
[1] https://github.com/pharo-nosql/voyage/issues/88
[2] https://github.com/pharo-nosql/voyage/issues/89
Le 31/03/2017 à 18:54, Paul DeBruicker
Or just store as ISO8601 string.
NorbertHartl wrote
> Hi,
>
>> Am 31.03.2017 um 17:16 schrieb Hilaire <
> hilaire@
> >:
>>
>> Hi,
>>
>> As far as I see when I store a DateAndTime with local time,
>> "2017-03-31T17:10:46.137086+02:00", then I fetch it back, I got an UTC
>> DateAndTime "2
Hi,
> Am 31.03.2017 um 17:16 schrieb Hilaire :
>
> Hi,
>
> As far as I see when I store a DateAndTime with local time,
> "2017-03-31T17:10:46.137086+02:00", then I fetch it back, I got an UTC
> DateAndTime "2017-03-31T15:10:46.137086+00:00".
>
> Am I doing something wrong or do I need to use a
Hi,
As far as I see when I store a DateAndTime with local time,
"2017-03-31T17:10:46.137086+02:00", then I fetch it back, I got an UTC
DateAndTime "2017-03-31T15:10:46.137086+00:00".
Am I doing something wrong or do I need to use a mongo description to
correct that. But wait, even so, I will not
