Bug #74086 for DBIx-Class-InflateColumn-Object-Enum: Setting an invalid value does not croak

Tue Jan 17 08:34:35 2012 ovid [...] cpan.org - Ticket created

Subject:

Setting an invalid value does not croak

It would be very handy if, when setting a new value, this module would croak() instead of silently refusing to set the new value.

Wed Jan 18 02:31:24 2012 jmmills [...] cpan.org - Correspondence added

If I remember correctly, the inflator just relies on Object::Enum to throw an exception. I'll add a bit of validation as soon as I move the code to github. On Tue Jan 17 08:34:35 2012, OVID wrote: Show quoted text

> It would be very handy if, when setting a new value, this module would > croak() instead of silently refusing to set the new value.

Wed Jan 18 02:31:25 2012 The RT System itself - Status changed from 'new' to 'open'

Fri Feb 10 15:23:26 2012 jmmills [...] cpan.org - Correspondence added

Just to make sure I'm understanding this correctly: This is when you try and do a $col->set_x where x is not defined as an acceptable enumeration value? Like __PACKAGE__->add_columns( color => { data_type => 'varchar', is_enum => 1, extra => { list => [qw/red green blue/] } } ); # later $col->set_pink; # should croak On Tue Jan 17 08:34:35 2012, OVID wrote: Show quoted text

> It would be very handy if, when setting a new value, this module would > croak() instead of silently refusing to set the new value.

Thu Feb 27 19:22:55 2014 jmmills [...] cpan.org - Taken

Fri Feb 28 19:41:02 2014 jmmills [...] cpan.org - Correspondence added

Altered behavior to allow Object::Enum to throw an exception. Of course this is deferred until the column inflator is called, which means doing a $rs->column($boom) won't trigger an exception immediately, only until DBIC decides to inflate it.

Fri Feb 28 19:41:03 2014 jmmills [...] cpan.org - Status changed from 'open' to 'resolved'

Fri Feb 28 19:41:03 2014 jmmills [...] cpan.org - Fixed in 0.05-TRIAL added