TrueFalse property optimized as a varchar(5)
Why does the default optimization on my setup produce a varchar(5) when I optimize the TrueFalse property? Shouldn't this be a BOOLEAN?
I noted a problem after optimizing that a report written to filter based on this property's "IsFalse" condition was raising an exception. At first, I believed it to be a data type mismatch but upon restarting the system everything shook out - even though the TF property exists in a database column as a varchar(5). I realize there's probably some "Pega-plumbing" going on to resolve this issue, but does anyone know if this is always the case with optimization of TF properties and why?
***Updated by moderator: Lochan to update Categories; add SR Exists group tag***
Accepted Solution
Pegasystems Inc.
US
Hi jpbecker,
Pega's True/False properties are varchar(5) when you expose the column, rather than Boolean as you'd expect for a True/False value.
This is per Pega's design because not all platforms have a "boolean" type (like Oracle).
Thanks,
Susan
Accepted Solution
Pegasystems Inc.
US
Hi jpbecker,
Pega's True/False properties are varchar(5) when you expose the column, rather than Boolean as you'd expect for a True/False value.
This is per Pega's design because not all platforms have a "boolean" type (like Oracle).
Thanks,
Susan