Skip to content

Passing custom doctrine type to addWhereByStrategy #3331

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

Closed

Conversation

oleg-andreyev
Copy link
Contributor

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tickets -
License MIT
Doc PR -

When usinguuid_binary_ordered_time (ramsey/uuid) as PK and then trying to filter list by association.id
ORM is not callingUuidBinaryOrderedTimeType because type is not passed to QueryBuilder parameters.

@soyuka soyuka force-pushed the custom-doctrine-type branch from 4ad1edb to 9204027 Compare April 15, 2020 14:48
@soyuka soyuka mentioned this pull request Apr 15, 2020
@soyuka
Copy link
Member

soyuka commented Apr 15, 2020

cs fixes unrelated, thanks @oleg-andreyev

@soyuka soyuka closed this Apr 15, 2020
soyuka added a commit to soyuka/core that referenced this pull request Apr 24, 2020
Adds correct deprecations to introduce back api-platform#3331
@bendavies
Copy link
Contributor

bendavies commented Apr 27, 2020

@soyuka This doesn't work with array values for WHERE IN queries, where the type should be Connection::PARAM_STR_ARRAY or Connection::PARAM_INT_ARRAY etc...
Surprised there isn't a behat scenario that covers this!

@guilliamxavier
Copy link
Contributor

FTR, this has been reverted (#3520) in version 2.5.6

@soyuka
Copy link
Member

soyuka commented Jun 22, 2020

re-opened in #3521 needs work though (don't hesitate to take it over)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants