| Subject: | 2 fields in different models with the same name collide EC settings |
EncodedColumn is exhibiting behaviour that, if a person creates a class
A with one encoding settings ( ie: none ) and a class B with different
encoding settings, but the encoding on a field with the same name, one
will overwrite the other, and you'll possibly either get a) no columns
encoded, or b) both columns encoded.
Proposed Patch Vs SVN 7824 That adds tests for this bug:
http://gist.github.com/222958
raw:
http://gist.github.com/raw/222958/890ebc8ad0debc7cdc6d7c34331e729b090b6351/gistfile1.diff
I have proposed a solution, which essentially involves substituting
$self->_column_encoders
with
$self->_column_encoders->{ $self->result_class }
in all the relevant locations.
Patch vs SVN 7824 that contains both my proposed solution and the tests :
http://gist.github.com/222959
raw:
http://gist.github.com/raw/222959/e988efd73c600db45682702b5786dbeef62ae13d/gistfile1.diff
nb. I could apply these myself, but I'd rather somebody vet them prior
to committing.