Lee Smith wrote: > 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.
I'm not talking about proprietary stuff. I'm talking about common stuff that's implemented in both DBs with different syntax. Generally one follows the SQL standard and one does not (e.g. standard and PG || vs. mySQL concat()). > 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. > Right. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
