On 1 February 2011 17:08, Clifford Heath <[email protected]> wrote:
> On 01/02/2011, at 5:02 PM, Daniel N wrote: > >> And until it's committed, if you try to read it, you will *block* or fail >> on a timeout/deadlock. >> What *won't* happen is that you get to see the data in either the before >> or after state. >> How do you mean Cliff? Do you mean from the connection inside the >> transaction that it can't be read? >> > > No, I mean that you can's see the change from any other transaction, say a > command-line SQL command or a database query tool. You'll only see the > results from within the transaction that created them. > > Clifford Heath. > > Cool, thanks for the clarification :D > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
