pgxstore expects a *pgxpool.Pool instead of a *sql.DB about scs HOT 5 OPEN

👍 Same, I can confirm that I've been running the pgx driver using postgresstore for scs without any issues thus far. A small suggestion would be to clarify in the readme of that adapter that is supports pgx as well as pq.

I'd be happy to open a quick PR to make that clarification if we agree 😊

from scs.

@tiagonbotelho Thanks, that sounds good to me 👍 It would be great if you could update the README for postgresstore to include examples of both using it with pq and also jackc/pgx/v5/stdlib. If we're making that change, we should probably update the table in the main SCS README at https://github.com/alexedwards/scs/tree/master#configuring-the-session-store too.

from scs.

To add to the issue description, one could definitely switch to using pq instead alongside the postgresstore. But pq does seem to point to pgx as the most up-to-date driver for Postgres.

from scs.

I guess another alternative would be to just use the postgresstore but instead of using pq like recommended in the README just use pgx 👍

I'll give it a try and report back. Maybe this is something that can be clarified in the README as well 😊

from scs.

I am using the pgx driver via the jackc/pgx/v5/stdlib interface to make it compatible to sqlx at. al., this works fine with postgresstore for scs. You can always get the pgx handle from the DB interface if you are so inclined to use the pgx interface.

from scs.