Hello Stephane,
Changing that behavior from using numeric 1/0 instead of char T/F in SQL Server has always been possible, and since version 3.5 (Jan-2017) it's documented as a simple option. Check "UseBoolean" in the following documentation topic:
Hello Stephane,