-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xsd:dateTime less than operator issue #630
Milestone
Comments
Equality operator doesn't work either.
|
Your first case, the problem is that your datetime syntax is wrong, if you change it to:
it works. The second problem is #615 |
This was referenced Mar 16, 2017
tgbugs
added a commit
to tgbugs/rdflib
that referenced
this issue
Nov 30, 2017
This commit provides basic infrastructure for sorting Literals by value where the underlying type has no total ordering. This provides a more consistent solution to issues like: RDFLib#648, RDFLib#630, and RDFLib#613. Where workarounds are implemented in the serializer. This leads to massively increased code complexity in the serializers to compensate for the fact that Literal do not support a total ordering because of some of the underlying python datatypes do not. The only datatype that I know of that causes this issue at the moment is datetime, and I have implemented a fix for that. If other types are found to have this issue the solution is to add an entry to _NO_TOTAL_ORDER_TYPES that includes a function that partitions the type into subtypes that do have total orders.
tgbugs
added a commit
to tgbugs/rdflib
that referenced
this issue
Nov 30, 2017
This commit provides basic infrastructure for sorting Literals by value where the underlying type has no total ordering. This provides a more consistent solution to issues like: RDFLib#648, RDFLib#630, and RDFLib#613. Where workarounds are implemented in the serializer. This leads to massively increased code complexity in the serializers to compensate for the fact that Literal do not support a total ordering because of some of the underlying python datatypes do not. The only datatype that I know of that causes this issue at the moment is datetime, and I have implemented a fix for that. If other types are found to have this issue the solution is to add an entry to _NO_TOTAL_ORDER_TYPES that includes a function that partitions the type into subtypes that do have total orders.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Filters on
xsd:dateTime
work with literals, i.e.But if there are two variables of
xsd:dateTime
then filter does not work properly, i.e.Script illustrating the issue below. It should show
c1
andc2
entities, but nothing is shown instead.The text was updated successfully, but these errors were encountered: