Ensure that BOOLEANS are TRUE|FALSE and not 0|1

[gavinbaumanis]

Description

Postgresql does not auto cast a 0|1 value to FALSE|TRUE - for Boolean types.

This PR changes 0|1 values -> FALSE|TRUE

Jira Issues

Bug Tracker: https://ortussolutions.atlassian.net/browse/CONTENTBOX-1541

Type of change

Please delete options that are not relevant.

• Bug Fix

Checklist

• My code follows the style guidelines of this project cfformat
• [N/A] I have commented my code, particularly in hard-to-understand areas
• [N/A] I have made corresponding changes to the documentation
• [N/A] I have added tests that prove my fix is effective or that my feature works
• [N/A] New and existing unit tests pass locally with my changes

My changes are correct but still fail because QB is "string-ifying" my boolean values from false to "false".

Nonetheless - Here is my PR - once QB is corrected - this PR will be appropriate.

[lmajano]

This looks good. However, we need to test against MySQL and the other databases.

[gavinbaumanis]

Hi Luis - thanks for the reply...

Message ID: ***@***.***>

I am happy to test with other DBs but cannot at the moment - because of the true|false booleans getting stringified. Eg: false -> "false" Here is the first of many errors I get from running the migrations [image: image.png]

[lmajano]

hi @gavinbaumanis we will be back 100% on things next week. Sorry for the delays, but the release of BoxLang and ITB really consumed our time. Hopefully, we can start closing a lot of these tickets soon.

FYI, your image did not come through?

[gavinbaumanis]

Hi @lmajano
Just thought I would give you a little prompt and see if the underlying issue of Booleans being "stringified" can be looked into, please?