I have a crazy issue I've been pulling my hairs about. In a docker entrypoint, echo $PATH shows the right path, running bash and executing the script works, but it magically can't find things in PATH when just running the container
I tried learning Blender long ago. Guess I didn't put in enough efforts or I am not of the artistic persuasion, but it was short lived and didn't turn out well.
I suspect the where in issue is a bug in the specific driver I'm using, I see no reason why it shouldn't work. I'm no postgres expert but I have a hunch. :P
@AndriyM It's actually weird. I could not get where .. in construct to work, but when I instead used where column = any($1::varchar[]) and passed in a list, the driver converted it properly to {item,item2,..} and passed it to postgres and it worked.
essentially I have a where column in ($1) somewhere in my query, and no matter what I pass as the positional param, if I have more than one item the query returns bad results.
