boolean needs to return a convertable value over the wire
Bug #708365 reported by
Monty Taylor
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Fix Released
|
Wishlist
|
Monty Taylor | ||
7.0 |
Fix Released
|
Wishlist
|
Monty Taylor |
Bug Description
When we return the boolean type, we need to return it as someting, probably an INT with a value of 0 or 1, which can be consumed by scripting language connnectors without additional context. The current varchar "TRUE"|"FALSE" is opaque at that level and causes test suite failures (specifically in sqlalchemy)
Related branches
lp:~mordred/drizzle/one-more-stab-at-boolean
- Andrew Hutchings: Approve
-
Diff: 630 lines (+272/-49)14 files modifiedclient/drizzle.cc (+127/-9)
client/drizzledump.cc (+7/-7)
client/drizzledump_data.cc (+11/-13)
client/drizzledump_data.h (+4/-7)
client/drizzledump_drizzle.cc (+4/-4)
client/drizzletest.cc (+38/-3)
client/include.am (+1/-0)
client/server_detect.h (+61/-0)
drizzled/field/boolean.cc (+2/-0)
libdrizzle/column.c (+1/-1)
libdrizzle/constants.h (+5/-1)
plugin/mysql_protocol/mysql_protocol.cc (+8/-1)
po/Makefile.in.in (+1/-1)
tests/r/show_check.result (+2/-2)
To post a comment you must log in.
Same problem for drizzle-jdbc
TIME is reported as TIMESTAMP and BOOLEAN as VARCHAR