Add support for "pgx" postgres driver/dialect. about testfixtures HOT 8 CLOSED

Hi @richard-to,

Great to know it kinda already works!

I think it's just a matter adding pgx to this switch as you said, and making sure there's a test for it.

from testfixtures.

Ok, great, I'll see if I can spin up a pull request next time I get the chance.

from testfixtures.

Closed as part of #74.

from testfixtures.

Hey guys, do you have an example of how to use this in code?

from testfixtures.

Hey guys, do you have an example of how to use this in code?

I believe you can set "pgx" as the dialect.

Here's a snippet from the readme.md that I modified:

        fixtures, err = testfixtures.New(
                testfixtures.Database(db), // You database connection
                testfixtures.Dialect("pgx"),
                testfixtures.Directory("testdata/fixtures"), // the directory containing the YAML files
        )

There's a comment there that says: // Available: "postgresql", "timescaledb", "mysql", "mariadb", "sqlite" and "sqlserver" So that can be updated I think to include pgx.

from testfixtures.

Thank you @richard-to . My confusion was how to get the "db" connection. It has to be stdlib.Conn and not pgx.Conn, correct?

from testfixtures.

Yes, you're right. You'll have to use database/sql with the pgx dialect . This should be fine since it's only for doing simple operations to manage the fixtures.

I do something like this in my code:

db, err = sql.Open(testConfig.Database.Dialect(), testConfig.Database.ConnectionInfo())

Then for my tests I use pgx directly. In my case I use pgxpool.

pool, err = pgxpool.Connect(context.Background(), testConfig.Database.ConnectionInfo())

from testfixtures.

Though I guess if you're using some very specific postgres features that don't work with database/sql, then this approach may not work

from testfixtures.