This project is archived and is in readonly mode.
Don't use the transaction instance method
Reported by Frederick Cheung | December 10th, 2008 @ 09:05 PM | in 2.x
Don't use the transaction instance method internally. The method is still there, but activerecord itself no longer uses it. This means that has_one/belongs_to transaction no longer kills your model
Comments and changes to this ticket
-
Repository December 10th, 2008 @ 11:12 PM
- State changed from “new” to “committed”
(from [455c7f9e37fda2969e52698b766413fc735eb488]) Don't use the transaction instance method so that people with has_one/belongs_to :transaction aren't fubared
[#1551 state:committed]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
-
Repository April 1st, 2009 @ 03:55 PM
(from [2dab082d0e1382eb0bc6a143bef6db8deebfd812]) Don't use the transaction instance method so that people with has_one/belongs_to :transaction aren't fubared
[#1551 state:committed]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Frederick Cheung
Attachments
Referenced by
-
1551
Don't use the transaction instance method
[#1551 state:committed]
-
993
Having column named 'transaction' in a model leads to weird behavior
Should be fixed by #1551 - overriding transaction shouldn...
-
1551
Don't use the transaction instance method
[#1551 state:committed]