I found that same link, thanks. If that's what it takes to get this
working, that's fine; but I still don't know why some 1.1.6 Rails
installations have this and two that I've run across don't. It's
considered a standard feature and is mentioned in the Agile book as
such.
Plus the date on the plugin says it was released 8/21/06, and I know
I've used it before then
I'm very confused. What other "standard" rails features might decide
to just not be there too?
I found that same link, thanks. If that's what it takes to get this
working, that's fine; but I still don't know why some 1.1.6 Rails
installations have this and two that I've run across don't. It's
considered a standard feature and is mentioned in the Agile book as
such.
Plus the date on the plugin says it was released 8/21/06, and I know
I've used it before then
I'm very confused. What other "standard" rails features might decide
to just not be there too?
I've got both the first and second editions of the AWDWR book as PDF, and neither of them mention db:fixtures:dump. Also I think if it was a standard Rails feature, it would appear in a lot more than 3 results when you Google it.
I'm using the manage_fixtures plugin, which provides db:fixtures:export_all - maybe that's what you previously used?
If you still have access to a system with a version of rails where db:fixtures:dump works, it might be worth grepping through your project directory (particularly vendor/plugins and lib/tasks) to see if you can work out how it's doing it.