Monday, July 4, 2011
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 <fredb001@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.FredOn Mon, Jul 4, 2011 at 19:04, Scott Ribe <scott_ribe@killerbytes.com> wrote:On Jul 4, 2011, at 5:24 PM, Andrew Skegg wrote:> environment where you fully control access to the underlying database...
> So long as you are in an
And where does one find such an environment in the real world???
--
Scott Ribe
scott_ribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment