On 17/03/12 08:02, Will Daniels wrote:
I'll admit my brain is a bit fried right now, but the logic seems crystal clear. Surprising as it is, I don't see that I could have made any mistake about this. Please check and advise.
Eventually I discovered that the problem does not exist when casting the string date explicitly to DATETIME, although I'm still unsure about whether or not this is a bug...certainly it is confusing for people more familiar with mainstream RDBMS where you can freely use strings as date literals without such concerns.
Virtuoso seems to do the implicit cast (almost) silently and returns expected results in most, but evidently not all cases.
-Will
