* Remove explicit requirement of rubygems
Oracle 10g support (all specs are green)
…like "ON DELETE NO ACTION" (which isn't really important because it's the default).
…sts?'. Table and constraint names must be uppercased.
Really unbreak the gemspec this time. I tested it in my fork.
I guess I don't know how to test the gemspec, short of installing it (but not into a bundle via :path, because that doesn't validate the gemspec).
Unbreak the gemspec.
Which I also broke in my recent reorganizing.
My previous refactor broke dm-constraints (despite tests passing). This fixes it again.
I had misread the previous implementation, and it seemed sensible to tie constraint creation to model migration. But no, there's a reason that constraints are all removed before migrating down, and all added after migrating up.
Better command/query separation (commands return self), pseudo-namespace methods piled into Model and Relationship. And one of my own, drop '!' on non-public auto_migrate methods, because there is no non-destructive alternative, that's just the behavior of the command.