…ith nothing mocked After a long wait, I've finally put together an integration test suite for sequel. Currently, it only covers the examples shown in the advanced_associations.rdoc file, but hopefully now that it is here, more people will contribute real specs. The integration specs have two ways of running, one where the database is specified, and one where it is not. If the database is not specified, it uses a sqlite memory database, and addition to checking for the correct functionality, it also checks that the correct SQL is being issued to the server. If the database is specified, it uses that database and ignores the SQL (since it can be different depending on the database). This gives the best of both worlds, the ability to check that sequel works with real databases, and the ability to see what SQL sequel is actual issuing to the server when nothing is mocked. Incidently, a prototype of this test suite is what helped me discover the Database#columns bug. You can run the integration test suite with "rake integration", and configure it via the INTEGRATION_URL constant in spec_config.rb, or via the SEQUEL_INTEGRATION_URL environment variable. While here, change the MYSQL_DB and POSTGRES_DB examples in spec_config.rb to MYSQL_URL and POSTGRES_URL, as it is preferable to use the URL instead of DB constant.
For merging the READMEs, I put the model README at the bottom of the core README and used that. For merging the CHANGELOGs, I merged them manually back to 1.4.0, and copied the rest of the model CHANGELOG to the bottom of the file. Most of the Rakefile code was duplicative, but I think I got all tasks except spec_adapters. I figure few people have all 5 adapters necessary to run the adapter specs. I only have 3 of them, so I never used spec_adapters. The specs are still split up so they can be run independently. Additionally, the adapter specs are split off from the core specs, which helps if you want to put Sequel.connect lines in spec_config.rb. The only other spec changes were for path changes. There weren't conflicts merging anything else, IIRC. I hope there is no fallout from this. I haven't noticed any yet, running the specs and the test suites for all of my apps that use Sequel.
…ss filters Add the doc/*.rdoc files to the list of RDoc files
Move stats.rb file from both sequel/extra and sequel_core/extra subdirectories, place in the extra directory in the root of the repository. Move the stress tests from sequel_core/stress to extra/stress. Remove the postgres_perf.rb stress test. Remove the TODO files, since I don't plan on implementing the suggestions therein. Remove the autotest files. Remove the sequel_core/examples files. Make the clean tests delete the temporary directories created, such as pkg, rdoc, and coverage.
This should fix the problem of gems not having the correct RDoc options. The directory structure is changing so that RDoc is now stored in rdoc instead of doc/rdoc. This is because doc is now going to hold additional documentation files.
…, plus some refactoring
…uel, sequel_core) Remove sequel directory/gem Rename sequel_model directory/gem to sequel Update Rakefiles to reflect renaming, remove some svn-related and misc cruft Bump versions of both sequel_core and sequel to 1.4.0 Remove TODO entry for associations, no longer needed Update CHANGELOGs
…where I left off.