#1704: Searchable behavior bug when primary key is not an integer -----------------------------------+--------------------------------------- -
Reporter: ctigglet | Owner: jwage
Type: defect | Status: new
Priority: minor | Milestone: Component: Searchable | Version: 1.0.3
Keywords: | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 1
-----------------------------------+--------------------------------------- - I discovered a bug where the Searchable behavior fails if the primary key
is anything other than an integer. I tracked the bug down and created the
attached patch.
Discussion subject changed to "#1704: [PATCH] Searchable behavior bug when primary key is not an integer (was: Searchable behavior bug when primary key is not an integer)" by Doctrine
Subject: Re: [Doctrine] #1704: [PATCH] Searchable behavior bug when primary key is not an integer (was: Searchable behavior bug when primary key is not an integer)
#1704: [PATCH] Searchable behavior bug when primary key is not an integer -----------------------------------+--------------------------------------- -
Reporter: ctigglet | Owner: jwage
Type: defect | Status: new
Priority: minor | Milestone: Component: Searchable | Version: 1.0.3
Keywords: | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 1
-----------------------------------+--------------------------------------- -
Comment(by romanb):
I think the original implementation as well as the patch are flawed. I
dont think databases other than mysql will allow numeric values to be
quoted. A proper solution would be to construct a prepared statement and
bind the parameters.