> This behavior is barely mentioned in the docs, and the author does not really accept any suggestions or criticism. This is where the programming community ha

> This behavior is barely mentioned in the docs, and the author does not really accept any suggestions or criticism. This is where the programming community has a role to play. When library authors blatantly brush off security issues, it's time to call out that behavior publicly and promote a secure fork. a database library should never have hidden behaviors such as theses. And "magics" such has manually building strings into a query like that s, or parsing a provided query to transform it into something else under the hood, should be turned off by default. This is absolute madness.