This is not a lot of work to change a type, as PostgreSQL allows type promotion. To copy data from one table to another (assuming compatible schema definitions): INSERT INTO db2.t2 SELECT FROM db1.t1 VIEWs have been around for a long time. But it would break compatibility with existing PostgreSQL databases or require to change type in existing databases. This would permit implicit cast between INT and BOOL. Share Improve this answer Follow answered at 9:57 Mchl 61.5k 9 118 120 But why bool and tinyint are different. 0 for false, 1-255 (preferably 1) for true. The vaules accepeted, are those for TINYINT i.e. I have no idea whether this is planned for D7 or not. 3 Answers Sorted by: 39 In MySQL BOOLEAN type is a synonym for TINYINT. PostgreSQL will cast data automatically in this case.Īnother possible would be to use PostgreSQL native boolean type in Drupal abstraction layer. Therefore, the solution is to write an explicit SQL query using 1 for true and 0 for false: SELECT delta, theme, weight, region, custom, throttle, visibility, pages, title The only reason for this is that Drupal abstraction layer considers that a boolean is an integer. Therefore the following query will execute under MySQL and fail under PostgreSQL: SELECT delta, theme, weight, region, custom, throttle, visibility, pages, title

For some reason, Drupal abstraction layer represents the binary type using an integer. PostgreSQL has a native binary type, which is able to cast automatically into integer and conversely when needed. There is no fundamental breakage in this assumption. MySQL considers that the boolean type is an integer type with value 0 or 1. Modern languages like Python allow lazy types and this does not beak the internal logic.

Also, a real boolean takes less space on disc than an integer. Therefore, SQL-99 makes no assumption and considers boolean as a seperate type from integer. It may also be NULL, which is a third value. SQL-99 standard does not consider that a boolean is an integer with 0 or 1 value.

Phpmyadmin boolean