raise_on_type_mismatch : expected User, got User
Reported by Lawrence Pit | May 20th, 2008 @ 08:49 PM
This issue is more than a year old and already extensively discussed at http://dev.rubyonrails.org/ticke....
Basically: when you have a model that has an association with another model that is part of a plugin, and on the second request your model gets reloaded in the development environment while the model in the plugin doesn't get reloaded, then assigning a new value to the association will result in an error like:
ActiveRecord::AssociationTypeMismatch: User expected, got User
Attached is a patch including a test to prove this case.
Comments and changes to this ticket
-
-
Pratik May 21st, 2008 @ 04:27 AM
- → State changed from “new” to “invalid”
Duplicate of http://rails.lighthouseapp.com/p...
-
Lawrence Pit May 21st, 2008 @ 06:11 AM
@Pratik : I suggest you look closer at my patch. It actually takes care of NOT showing the error message, something that ticket #189 does not do.
-
Pratik May 21st, 2008 @ 06:24 AM
Yes I noticed.
1. The tests pass even without the patch. Also, the patch is in wrong directory. Should be in ar/test/cases/
2. Not really in favor of putting eval stuff. I.e. magically reloading plugin model.
3.People should just make plugins reloadable instead.
Thanks.
-
Roger May 21st, 2008 @ 11:05 AM
I wonder if it couldn't use something like
if is_a?(klass) or is_a?(eval(klass)) # only use the eval as a backup...
-R
-
Lawrence Pit May 21st, 2008 @ 04:55 PM
@Roger that is what it's doing, it's only used as a backup
@Pratik the test was in the wrong dir, I've attached two new files: one with the test, one with the patch. If you run the test it does NOT pass without the patch.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
Kamal Fariz