Closed andreyvk closed 9 years ago
Thenk you @andreyvk , i will investigate
I'm happy I could help really. And thanks for great job on this library :)
Hi, I had the same problem with DateTimes and fixed it (for now), by replacing this line:
return $value->getTimestamp() . 't';
by this one:
return $value->getTimestamp() . '000t';
(vendor/ostico/phporient/src/PhpOrient/Protocols/Binary/Serialization/CSV.php:530)
In my understanding we get this bug because the 'getTimestamp()' method does not return the milliseconds.
Hope that helps!
Hi @pjmazenot ,
the patch you suggested is good. I'm updating.
Glad I could help. Thanks @Ostico for this library, I just started using OrientDB and it saved me a lot of time!
Thanks @pjmazenot! Looking forward for an official patch
Hi,
I think there's a problem saving date/datetime fields, while updating records. Looks like problem is with converting DateTime object into date data, when saving a record. Im on the latest PhpOrient using OrientDB 2.0.10.
Here's the schema + test record:
In the console:
Executing the following saves wrong date data:
Select again (see date data lost):