-
Notifications
You must be signed in to change notification settings - Fork 60
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
date literal in query invalid #153
Comments
can you locate a bit more what triggers the exception? is it triggered during the generation of the sql statement? is it triggered while executing the generated sql? or some where else? |
i stumbled over the same, it seems our SQL2 parser does not handle the |
@rmsint is this fixed with what lukas just did on phpcr-utils tonight? phpcr/phpcr-utils#99 |
ping |
Ah yes, I will do a test somewhere the next days. |
hi @rmsint this is the only remaining blocker for releasing 1.1. can you check it maybe this weekend? would be awesome. |
hi @dbu actually I am currently checking it using the symfony-cmf website as test case. Currently the query is not giving an error, however also no results while it should. I have to check it a bit more. The case is that if we have some upcoming talks the query should return the talks that happen after the current date. |
After some more checks imho the date literal issue is solved. However using dbal together with sqlite gives no results for a query using the date literal, I think this caused by another issue. For jackrabbit and dbal mysql the query with a date literal is giving the expected results. On the cmf-sandbox, this query:
should give 2 results:
The generated sql is:
The difference is that:
|
thanks a lot. i created #174 to follow this up. |
Creating this query using the QueryBuilder:
generates this sql-2 query:
Running the query using
app/console doctrine:phpcr:workspace:query
tells the query is in invalid (PHPCR\Query\InvalidQueryException), and in code returns no results.Running the same query when using jackalope-jackrabbit is succeeding.
The text was updated successfully, but these errors were encountered: