Alan

This works for me now, if you have a column (blah) of type tinyint(1) you can reference it like this:

obj.blah? #-> true obj.blah=false

Recognize tinyint(1) as a proper boolean type

Using AR 1.9.0, found this change insufficient, as the proper value wasn't put back in the DB, so I modified also the type_cast and quote functions.

Done at the Mysql adapter level. It treats any tinyint(1) as boolean.

I can't produce any issues. Please elaborate as to the error. What is the improper value? What would the proper value be? Use snippets of the code controlling the model, and pieces of the sql log as evidence. For extra marks, submit a test case which illustrates the error. (It must fail, obviously.)

I've had problems with bool (TINYINT(1)) and MySQL too. Basically ActiveRecord won't translate 'obj.blah = true' into '1' in the database. I can't remember exactly what it does, but I think it tries to set it to the string 'true' and fails, and the value in the database doesn't get changed. Up to now I've been using explicit '1' and '0' values in my Ruby code to get around this.

I'll put together a test case that demonstrates this and post it here when I'm done.

What I'm doing is defining the tinyint(1) as the boolean of mysql, so listings show true and false by default, instead of whatever value and 0, respectively. Seems better to me than doing it at application level, maybe with a (non implemented) model option which allows to declare any integer field as a boolean, instead of mandatory on tinyint(1).

This is still broken in the current release, scaffolding fails to recognise it as boolean so i assume its not working.

the attached patch while fixing the display issues, does not actually work for setting values etc as mentioned by the others.

Essentially, booleans in mysql are totally non operational. There is some code in the mysql activerecord adapter for tinyint(1) being boolean but nothing seems to recognise this,.

You're referring to a different problem here, scaffolding not recognising booleans. Could you please open another ticket for it

@object.property?

will work

ahh ok my mistake, sorry :)

I think this is problematic. Working with a legacy database, a column may be specified as TINYINT but not be used for boolean types(i.e. it may store more than two distinct values)

There should be a way to disable this in a model

ahh never mind, I found *_before_type_cast ... just took a little while. sorry for the trouble

Also, note that the width field is only used for display in mysql--it does not affect the actual storage size of the data. Thus, tinyint(2) would be interpreted as an integer, while tinyint(1) would be interpreted as a boolean.

In general, it is probably not worth differentiating between integer and tinyint for integer uses, disk storage capacity being what it is these days. However, using tinyint(2) is, I think, an acceptible workaround.

ladies dress watches lucas luggage merrell hiking boots electric sunglasses gucci sunglass hiking boots retail franck muller watches cowboy boots for women willys jeep truck danner boots new balance shoes diehard work boots discount brighton purses franck muller watches dior sunglasses jeep grand cherokee black diamond lift kits shoes nike running shoes online boots motorcycle wholesale jungle boots bostonian shoes dragon sunglasses asics running shoes jeep cherokee roof rack equestrian riding boots

Good design! <a href="http://yzpgwwxm.com/jfgr/kqwh.html">My homepage</a> | <a href="http://ecklvtqu.com/iaro/zrwv.html">Please visit</a>