Running AR Tests with Postgres-PR

Has anyone successfully run the AR tests with the pure ruby postgresql driver?

I am seeing a bunch of these:

ActiveRecord::StatementInvalid: NoMethodError: undefined method
`async_exec' for #<PGconn:0x3258dcc>: SET client_min_messages TO
'warning'

I want to make sure I'm executing the tests correctly first before I
go and try to patch the Postgres driver.

Right now I'm just executing with:

  rake test_postgresql

Thanks.

V/r
Anthony Eden

I don't get that error, but I'm not 100% sure if I'm using the pure ruby driver either. Judging by the gem list I don't have any postgres driver gem installed. I am getting a bunch of schema-related errors, though, but I think that's because of some weird permission issues.

//jarkko

Those errors (5 of them, I think) are chained. The first test errors out because it tries to create a new schema with a new role as owner. (You should grant role creation permissions to the user you’re testing with.) The role is created, but the schema isn’t and the consequent tests fail because of it.

Jarkko, I don’t think you can connect to Postgres database without any of the following: postgres, ruby-postgres, postgres-pr. I’m using ruby-postgres with Rails 1.2, using postgres spews out much more errors, almost all regarding an auto-increment primary key column (id) being given NULL as value (primary keys are NOT NULL).

-M

Those errors (5 of them, I think) are chained. The first test errors out because it tries to create a new schema with a new role as owner. (You should grant role creation permissions to the user you're testing with.) The role is created, but the schema isn't and the consequent tests fail because of it.

Yeah, that's what I figured and didn't thus pay much attention to it.

Jarkko, I don't think you can connect to Postgres database without any of the following: postgres, ruby-postgres, postgres-pr. I'm using ruby-postgres with Rails 1.2, using postgres spews out much more errors, almost all regarding an auto-increment primary key column (id) being given NULL as value (primary keys are NOT NULL).

Heh, yeah, I didn't mean I wouldn't have any of them, just that the gem list didn't give an obvious answer. Actually I think this port is the one that's used:

rb-postgres @0.7.1_4 (active)

//jarkko