On 17.1.2007, at 21.21, Mislav Marohnić wrote:
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 -- Jarkko Laine http://jlaine.net http://dotherightthing.com http://www.railsecommerce.com http://odesign.fi
smime.p7s
Description: S/MIME cryptographic signature
