-
Notifications
You must be signed in to change notification settings - Fork 29
qom always has a selector name #86
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
Conversation
default: | ||
// Exit loop for debugging | ||
break(2); | ||
throw new InvalidQueryException('Expected end of query, got ' . $this->scanner->lookupNextToken() . ' in ' . $this->sql2); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was never cleaned up
kind of strange that the tests are passing .. but i guess we do not have any query tests in here. |
yeah we need a qom factory implementation to do that seriously. so the |
so lets merge? |
this needs to be coordinated with the other 3 PR on phpcr and phpcr-api-tests and jackalope - did you look into them as well? |
the composer.json should also be updated even if we do not yet have the necessary tag |
i updated composer.json and merged phpcr already as we depend on an exact version there. this PR needs to be synchronized with jackalope as we depend on |
we also need to fix QueryBuilder::select and addSelect |
qom always has a selector name
adjust phpcr-utils to phpcr/phpcr#68