Open rrichardson opened 3 years ago
Hi !
Nope, the issue you are refering to is not about parsing multidimentional arrays (nor parsing literals, for that matter). Thanks to have checked for duplicate though :)
I'm a bit busy this week, but I will fix it asap. Thanks for the report.
@rrichardson / @oguimbal : Any update for this as we are still facing issue with substring(_id :: text from 3):: uuid ::text = any ( ARRAY[ARRAY['a521ce02-ecc9-4bb2-9578-d422a7b85a33']]:: text[]); failing with below error : 'Cannot be evaluated as constant\n\nš„ This is a nasty error, which was unexpected by pg-mem. Also known "a bug" š Please file an issue !\n\nļøā£ Failed SQL statement: 'QueryFailedError: Cannot be evaluated as constant\n\nš„ This is a nasty error, which was unexpected by pg-mem. Also known "a bug" š Please file an issue !\n\nļøā£ Failed SQL statement:
This statement works in postgres 9.3+
However, this results in a parsing error at the second open bracket:
This looks like it was supposed to be fixed in 1.6.1 (https://github.com/oguimbal/pg-mem/issues/50) so it might be a regression.
Unfortunately I can't work around it with array literal syntax, since I need to dynamically assign a variable in the array.