ParanoidDateTime doesn't work with STI
Reported by inspired | July 29th, 2008 @ 03:05 AM
#type in a STI model was sometimes nil and other times not nil. Commenting out property :deleted_at, ParanoidDateTime
fixed the problem, as adviced by dkubb.
dkubb: inspired: I did notice some weirdness in edge DM with ParanoidDateTime. Just as a small test, try commenting out that property and see if the problem persists
This might be a problem with ParanoidDateTime used together with STI or just ParanoidDateTime.
Comments and changes to this ticket
-
Dan Kubb (dkubb) January 8th, 2009 @ 02:20 PM
- State changed from “new” to “unconfirmed”
- Assigned user cleared.
-
Michael Klishin (antares) January 10th, 2009 @ 06:28 AM
- Tag set to “dm-types, sti”
- Assigned user set to “Michael Klishin (antares)”
- Title changed from “ParanoidDateTime - doesn't work with STI” to “ParanoidDateTime doesn't work with STI”
-
Dan Kubb (dkubb) February 21st, 2009 @ 01:30 AM
- Assigned user changed from “Michael Klishin (antares)” to “Dan Kubb (dkubb)”
- State changed from “unconfirmed” to “not-applicable”
I am unable to reproduce this problem with dm-core/next. The attached script works as expected.
inspired, if you can alter the attached script to reproduce the problem please add a comment to this ticket and I will reopen it. Marking this as not-applicable for now.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Michael Klishin (antares)