Change postgresql boolean column type to BOOLEAN

[kbanman]

Creating a boolean column with Schema under postgreSQL results in a SMALLINT column type. Unlike MySQL, PostgreSQL has a real boolean type distinct from small integers.

If you don't agree with this change, could you point out how one might use Schema to create proprietary column types such as the above?

[vpetrov]

same for mysql.

[mark-poulsen]

The problem with boolean columns in posgresql is that they appear as string 't' or string 'f' in php. That is really bad since they both equals to true when you do comparisons. So it is therefore good practice to use a bit or integer column instead.

[vpetrov]

Is the PostgreSQL driver able to convert 't' and 'f' values for boolean columns to PHP true/false when results are returned? Or, is it able to change the SQL queries such that boolean columns are cast to integers, like so: "SELECT b::integer ..." ?

In MySQL, BOOL is a synonym for TINYINT(1), which obviously works fine. However, Laravel currently generates TINYINT(4). Why waste 3 extra bytes for every row on every boolean column?

[Furgas]

I'm using PDO for PostgreSQL and boolean column values are converted to PHP true/false, not 't'/'f'. Since Laravel is using PDO for PostgreSQL I think that this change is very much needed.

[taylorotwell]

Don't want to change this in Laravel 3.x as it could break people's applications. Will consider for Laravel 4.

[JoshZA]

@taylorotwell - If you choose to implement this, please be aware that it needs to be done using the following method when assigning false bools -> yiisoft/yii#779

[ar45]

TINYINT(4) does not take up more space, it just changes how many digits to display.