Functional tests vs SQLite3's transactions

Rails
1

Railsters:

I have just started a Rails site. I got SQLite3 working sooner than
MySQL, so I went with the former.

Then I ran ‘rake test’, and received major spewage, including this:

cannot rollback - no transaction is active (SQLite3::SQLException)

Then I installed Salted Hash Login Generator, and README_USER_LOGIN
told me:

“Whatever DB you use, it must support transactions.
If it does not, the functional tests will not work properly…”

Then I googled for SQLite’s situation, and got this:

http://web.utk.edu/~jplyon/sqlite/SQLite_optimization_FAQ.html

“Although SQLite parses named transactions, the names are ignored.
SQLite does not support nested transactions.”

So which is it? Will SQLite3 work, and support the functional tests, or
do the functional tests require named or nested transactions? Or is
something else going on?

–
Phlip

2

Aaaaaand when I switch to Win32 and switch to MySQL, all the errors go
away.

So it looks like SQLite3’s transactions do not satisfy the SHLG.

I also get a new rump-load of errors like these:

  1. Failure:
    test_auth(UserTest) [./test/unit/user_test.rb:9]:
    expected but was
    <#<User:0x3c830f8
    @attributes=…

So off I go Googling and FAQing again! (-;