Am 03.01.2019 um 22:52 schrieb Justin Pryzby:> One thought ; should
"name" be an kwarg with default name='' ?
It's now implemented that way. But I noticed an issue with unnamed
queries. It seems like Postgres replaces the unnamed query as soon as
it's running any other query. That means any query that the DB wrapper
is running behind the scenes (e.g. to fetch types) or you are running in
your code between query_prepared() calls will destroy the unnamed query.
So this makes unnamed query really not that useful and we should
discourage using them. The question is then, should we not revert that
change and use a positional argument for the name again. That's more
convenient than a keyword-only argument if you need to set it anyway
every time.
-- Christoph
_______________________________________________
PyGreSQL mailing list
[email protected]
https://mail.vex.net/mailman/listinfo/pygresql
