fActiveRecord cannot handle MySQL tables that have columns of BIT(1) default value 0 #81

jeffturcotte opened this Issue Jul 10, 2012 · 0 comments

1 participant

Flourish member

Ticket #671 by Connor

I understand this may have been by design to discourage the use of BIT(1). It should hardly affect developers since they can use TINYINT(1) instead.

Comment by Connor

Here are more details: if the table has columns of BIT(1) default value 0, where class A extends fActiveRecord for that table,

then this evaluates:

$myrecord = new A();

but this will throw an fProgrammerException:

$myrecord = new A(array('name of some unique key' => 'value of that unique key'));

Comment by @wbond

Can you paste the exception message and backtrace?

Comment by Connor

Fatal error: Uncaught exception 'IneffectiveSubmissionException?' in /opt/wysperwyre/controller/UserController.php:43 Stack trace: #0 [internal function]: UserController?->login('dennis', 'password') #1 /var/www/wysperwyre.com/index.php(78): call_user_func_array(Array, Array) #2 {main} thrown in /opt/wysperwyre/controller/UserController.php on line 43

IneffectiveSubmissionException? and UserController? are classes which I wrote for my application, of course.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment