(rant) Since Rails devs don't appear to believe in databases (and to be fair, if I was targeting MySQL version 3 I'm not sure I would believe in them much either), they don't bother using database features for binding. Instead having their own half baked (well, it 90% baked now, but it still has the occasional squishy bit) binding system.
Same for validations, foreign keys, primary keys, indexes, enumerations, etc. (/rant)
the places where these sql injections were happening wouldn't be prevented from traditional sql bindings which are applied to parts of the where clause or set values. in JDBC land i don't think you can do "SHOW TABLES FROM ? WHERE ...."
You could, but that solution isn't of much help to someone with an existing .NET/SQL Server application. Making a few tweaks is probably a lot cheaper than a wholesale change to a different database server.