Rails core - Dec 2005 - connection specifications borked in changeset 3218?

Hi,

it looks like a recent change (3218) has borked connection  
specifications in some way.

When I run my unit tests it fails because even though it''s connection  
to the test database it''s using the username (and I presume,  
password) of the *development* user.

This does not occur in 3217 and, of course, it isn''t a problem if you  
happen to use the same login and password for all three databases...

By the way, does this sort of ''oops'' thing deserve a TRAC
entry as a
first point of contact or is it ok to send these to this list?

Thanks for looking,
Trevor

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Dec 5, 2005, at 12:55 PM, Trevor Squires wrote:
> it looks like a recent change (3218) has borked connection  
> specifications in some way.
>
> When I run my unit tests it fails because even though it''s  
> connection to the test database it''s using the username (and I  
> presume, password) of the *development* user.
>
> This does not occur in 3217 and, of course, it isn''t a problem if
> you happen to use the same login and password for all three  
> databases...
>
> By the way, does this sort of ''oops'' thing deserve a TRAC
entry as
> a first point of contact or is it ok to send these to this list?
Please raise issues loudly and in every available forum :)

I fixed the problem in [3222].

Thanks,
jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD4DBQFDlLZ0AQHALep9HFYRAqzgAJ9k9gESpeVoZKVY0gTxpGbuWpdbqACXTTUl
YBuUT/QprG8ScYuJt4MmvQ==ZUgP
-----END PGP SIGNATURE-----

> Please raise issues loudly and in every available forum :)
I''d like to suggest that more traffic on this list is a good thing.  
That would also be my suggestion to Francois.

If you discuss patches here, I''m more than happy to apply them as it
gets more ''eyes'' on it than a trac ticket does.

--
Cheers

Koz