PostgreSQL, problems with Boolean type storing values as "T" and "F" breaking ORM

dapper npgsql postgresql

Question

If I define a boolean data type in a Postgres table and query from it, the results for the boolean columns come back as "t" or "f".

I'm using NPGSQL as my driver and Dapper as a ORM. This causes a problem because Dapper is unable to convert "t" or "f" into a boolean value, and all boolean values end up as False.

Is there a way to change this behavior with Postgres, or do I need to hack around it by using a character data type?

Accepted Answer

Cast it to integer to get 0 or 1

SELECT boolean_value::INT ;

or to varchar to get 'true' or 'false'.

SELECT boolean_value::VARCHAR ;

Most DB drivers should be able to handle the one or the other.




Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Is this KB legal? Yes, learn why
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Is this KB legal? Yes, learn why