Closed maxbes closed 2 years ago
If a user accidentally sets the "Index" parameter when using PgJSON, session creation fails with (eg)
[error] Session cannot be tied: DBD::Pg::st execute failed: ERROR: column "_whattotrace" of relation "sessions" does not exist
The reason is that PgJSON declares its store to be Apache::Session::Browseable::Store::Postgres which uses the "Index" option
Apache::Session::Browseable::Store::Postgres
It should probably use Apache::Session::Store::Postgres instead, so that the "Index" option won't interfere
Apache::Session::Store::Postgres
Low priority issue, this only causes problems in a configuration that is wrong to begin with
Wrong: backend just enables UTF8. No issue here, just a wrong config :wink:
If a user accidentally sets the "Index" parameter when using PgJSON, session creation fails with (eg)
The reason is that PgJSON declares its store to be
Apache::Session::Browseable::Store::Postgres
which uses the "Index" optionIt should probably use
Apache::Session::Store::Postgres
instead, so that the "Index" option won't interfereLow priority issue, this only causes problems in a configuration that is wrong to begin with