That logic applies to all the databases. The moment you use proprietary database functions in your SQL, you have just locked yourself in to using that database vendor. That same function may or may not exist with another database vendor. Not that it's a bad thing, just that your code is not database independent.
On Sep 3, 9:55 am, Marnen Laibow-Koser <rails-mailing-l...@andreas- s.net> wrote: > That's true, of course. And I've used PostgreSQL for dev with mySQL in > production. However, I was under the impression that SQLite simply had > no equivalent for a lot of fairly common PG or mySQL tasks. I was also > under the impression that if you need, say, a custom :conditions string, > SQLite's syntax is likely to be different from the other two. I could > be wrong. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
