Good point. I was only talking about ad hoc access not regular access from outside of Rails. That doesn't seem possible -- or at least shouldn't be.
Fred On Mon, Jul 4, 2011 at 21:41, Fred Ballard <fredb...@gmail.com> wrote: > In a large scale environment, there may be times when someone accesses the > database directly, bypassing Rails. > > This may include the DBAs, for instance, or even the maintainers of the > system. > > This may happen in trying to resolve a production problem in as short a > time as possible, and it seems like a good idea at the time to access the > database directly. > > Fred > > On Mon, Jul 4, 2011 at 19:04, Scott Ribe <scott_r...@killerbytes.com>wrote: > >> On Jul 4, 2011, at 5:24 PM, Andrew Skegg wrote: >> >> > So long as you are in an >> > environment where you fully control access to the underlying database... >> >> And where does one find such an environment in the real world??? >> >> -- >> Scott Ribe >> scott_r...@elevated-dev.com >> http://www.elevated-dev.com/ >> (303) 722-0567 voice >> >> >> >> >> -- >> 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. >> >> > -- 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.
