Also fix callers that were checking for t/f. In CASE and COALESCE expressions, using 't' and 'f' did actually work, because those literals have an unknown type and the other argument is boolean, so PG coerces them to boolean. But it seems safer and clearer to use the strongly typed literals TRUE and FALSE. Bug: T352229 Change-Id: Ia01b76d3d6d2e048feac8e3118d9faff63a9ac56 |
||
|---|---|---|
| .. | ||
| api-testing | ||
| common | ||
| parser | ||
| phan | ||
| phpunit | ||
| qunit | ||
| selenium | ||
| .htaccess | ||