the update:
After writing a little test case that fails under the current system and giving a few tests I've actually found that my particular issue is only with SQLite3. Now, while testing I've actually found that the transaction system is not very friendly generally! ... it doesn't correctly remember when it has opened transactions and also is insistant on COMMITing transaction that have been ROLLBACKed ... [this is actually where my problem lies] so...I've decided to fix it... So far my fixes work on postgres and mysql and include: ** moving the object level transactions into their own module (ready for depreciation) ** properly ensuring transactions are ended correctly (no more postgres warnings!) is it me or does SQLite3 fall flat on it's face in the tests? ... it fails badly on my macbook and my solaris systems... is this known or have just installed SQLite with my eyes closed? thanks for your help. oh..and... what initiates the migrations for the tests?... I can't find it and think this is where my sqlite3 test issues lie? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
