mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-1967: mysql Tiny ints not behaving properley #2482
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Aug 4, 2012).
Originally assigned to: @beberlei on GitHub.
Jira issue originally created by user jonathanpete:
If I set up a field as a tinyint lets say called bob. I then extract a record.
If I do $object->getBob() - when bob = 1, everything works fine.
However, if I do $object->getBob() when bob = 0, the null value is returned.
If bob is null, everything works fine.
This issues only seems to happen with mysql tinyint.
@doctrinebot commented on GitHub (Aug 14, 2012):
Comment created by @asm89:
I guess it is 'false' that is being returned? That's because MySql's tinyint will be mapped as boolean (by doctrine dbal).
@doctrinebot commented on GitHub (Aug 28, 2012):
Comment created by jonathanpete:
No. The value "" is returned as in an empty string.
@doctrinebot commented on GitHub (Aug 29, 2012):
Comment created by @beberlei:
can you show your mapping for this value?
@doctrinebot commented on GitHub (Oct 9, 2012):
Comment created by jonathanpete:
Sure. Mapping is:
DBAL maps field as a tiny int. If I manually set field to 0, DBAL returns null. If I set to null, DBAL returns null. If I set to 1, DBAL returns true.
@doctrinebot commented on GitHub (Oct 10, 2012):
Comment created by jonathanpete:
I installed the new version, then reverted back and the problem seems to have gone away. I'm very confused!! Perhaps it was an installation problem at my end. But can't think what. Oh well...
@doctrinebot commented on GitHub (Oct 10, 2012):
Comment created by jonathanpete:
nope, i'm wrong. it is a bug - something else fooled me into thinking it was working. I have tried setting up other boolean data fields and the same issue occurs.
@doctrinebot commented on GitHub (Oct 10, 2012):
Issue was closed with resolution "Invalid"