description: With Firebird 3.0 a secondary condition after a between condition is not accepted (due to new Boolean type presumably) whereas it is accepted in Firebird 2.5
I do not know if it is "as designed" but I did not see any warning about this in the release notes.

select * from rdb$database where rdb$relation_id between 1 and 500 and rdb$description is null; --Is working in FB2.5 and give < Invalid usage of boolean expression. > in Firebird 3.0
select * from rdb$database where rdb$description is null and rdb$relation_id between 1 and 500; -- Is working in both versions.

=>

With Firebird 3.0 a secondary condition after a between condition is not accepted (due to new Boolean type presumably) whereas it is accepted in Firebird 2.5

--This works in FB2.5 and v3.0
select * from rdb$database where rdb$description is null and rdb$relation_id between 1 and 500;

--This works in FB2.5 but fails in v3.0 < Invalid usage of boolean expression. >
select * from rdb$database where rdb$relation_id between 1 and 500 and rdb$description is null;

summary: second condition after a between condition raise error (Invalid usage of boolean expression) => Regression: second condition after BETWEEN condition raise error (Invalid usage of boolean expression)

assignee: Adriano dos Santos Fernandes [ asfernandes ]

summary: Regression: second condition after BETWEEN condition raise error (Invalid usage of boolean expression) => Wrong evaluation of BETWEEN and boolean expressions due to parser conflict

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 2 [ 10560 ]

summary: Wrong evaluation of BETWEEN and boolean expressions due to parser conflict => Regression: Wrong evaluation of BETWEEN and boolean expressions due to parser conflict

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: Done successfully