DHH wrote: >> What's the point of having different dbs if app frameworks reduce them >> to some wimpy lowest common denominator. > > Why even bother with SQL, then :)? Why not just give every database > their own query language that's designed just for them. There are > other reasons than API to pick different databases (like performance, > storage engines, replication facilities, etc).
ok, well, that fork is headed nowhere, but I still don't see what the heck the catastrophe is behind allowing the database to accept defaults it deems as valid, even resorts to, in its own API. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
