We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
as discovered with jackalope/jackalope#301, we seem to have a duplication of the selector name. why do we under some circumstances add the selector name to dcr:name in https://github.com/jackalope/jackalope-doctrine-dbal/blob/master/src/Jackalope/Transport/DoctrineDBAL/Client.php#L2329 ? having it in dcr:selectorName would be enough (and actually simpler) for jackalope.
The text was updated successfully, but these errors were encountered:
I am pretty sure all of this was initially created with little understanding of things and just trying to emulate Jackrabbit as much as possible.
Sorry, something went wrong.
in this case, jackrabbit is not adding the selector in the column name, and only the order of the code in jackalope led to correct column names.
No branches or pull requests
as discovered with jackalope/jackalope#301, we seem to have a duplication of the selector name. why do we under some circumstances add the selector name to dcr:name in
https://github.com/jackalope/jackalope-doctrine-dbal/blob/master/src/Jackalope/Transport/DoctrineDBAL/Client.php#L2329 ? having it in dcr:selectorName would be enough (and actually simpler) for jackalope.
The text was updated successfully, but these errors were encountered: