Validates Timeliness triggers an error in a class where it's not used.. about validates_timeliness

[adzap]

Hi,

This is a side effect of a unfortunate design decision on my part for version 2, which is to override the date/time parsing of all such columns regardless of validation done on them. It was initially to give the most correct time and date parsing available. But it is unexpected consequence of this version of the plugin. I changed this in version 3.

This issue here is being caused by the assignment of an integer to a date/time attribute. The plugin assumes all these columns are being used as time or date values and not to store a duration.

Is this a duration you are storing?
What is the database type?

[dlupu]

Hi,

Thanks for answering so quickly. Indeed i'm storing a duration. I use mysql.

Since I can't migrate on Rails 3 yet, is there a workaround?

Thakns!

[adzap]

Not easily at the moment. Perhaps try assigning Time.at(1.second) for seconds since epoch. But I have never used a duration column before, so i don't know it's correct usage.

Otherwise I will have to add an attribute exclusion list to v2.3.

[dlupu]

Hello

Sorry for answering only now. I tested your suggestion but it didn't work.

However current_wt.online = "00:00:01" seems to do the trick :)

[adzap]

I was under the impression there was a mysql database type of duration. It seems there is not so I will close this ticket as the plugin won't support fixnum assignments.

If the plugin is overriding the write accessor it means the column you are using is a date/time data type. Perhaps using this data type for a duration column is not a wise choice.