Shawn Poindexter
Shawn Poindexter
I've created a PR for a test case for this. I cannot get it to fail on OrientDB 1.7.9, 2.0.1 or 2.0.2. Can you please try this test case on...
Good point. I'll take a look and see what I can figure out.
I'm having trouble figuring out how this can be accomplished with the binary protocol which `OTransaction` is using. The [REQUEST_TX_COMMIT](https://github.com/orientechnologies/orientdb/wiki/Network-Binary-Protocol#request_tx_commit) documentation only lists three operations: `UPDATES`, `DELETIONS`, and `CREATIONS`. Maybe...
The following NUnit snippet works on my machine. ``` c# database.Create.Class("myClass").Run(); var doc = new ODocument { OClassName = "myClass" }; var date = new DateTime(2015, 02, 08); doc.SetField("Date", date);...
I am able to reproduce it in a test case in my latest PR. The date is correct in the database but when it is retrieved it is moved forward...
@bnoffer You should be able to work around this problem by executing ``` ALTER DATABASE TIMEZONE UTC ```