On Tuesday 06 March 2007, John Siracusa wrote:
> On 3/4/07, Cory Bennett <[EMAIL PROTECTED]> wrote:
> > Any ideas or work arounds?
>
> Looks like a bug. The only workaround I can think of is to use the
> unset_column_value_modified() function from Rose::DB::Object::Util.
> I'll work on a fix...
Cool, thanks. I found another hacky work around. It seems to work fine if
you change the column definition from:
enum_val => {
type => 'set',
default => 'A',
values => [ 'A', 'B' ]
},
to
enum_val => {
type => 'varchar',
length => '255',
default => 'A',
check_in => [ 'A', 'B' ]
},
So I just have to trick Rose into thinking my Enum columns are Varchar columns
with a check_in trigger. There might be complications with this, but I have
not seen any yet.
-Cory
>
> -John
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Rose-db-object mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/rose-db-object
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rose-db-object
