I’m trying to post the problems and the solutions in this blog.

I was seeing a similar NoMethodError with

@examples = example.find(:first)

in the controller, which resulted
in the following SQL (see your web server console output):

SELECT * FROM `examples` LIMIT 1

Apparently the corresponding “each” method in my views/index.html.erb file
(below) doesn’t work on a single record.

% @examples.each do |c| %>
’show’ } %>

When I changed the contoller method to:

@examples = example.find(:all)

The LIMIT 1 was no longer in the SQL query:

SELECT * FROM `examples`

And “each” worked.

I can still delete a valid date from my form.

A couple things to check:
- The field value should be empty when the user saves the form. Can you verify that the controller correctly get an empty string from the field?
- Are you sure the date is not protected field?

Handy

One problem i’ve come across is that it seems impossible to change a date to nil from a valid date once it is set - any ideas ?

Interesting idea… I’ve never thought about doing the embedded calendar since I think the form looks more clean for my project. Different projects have different requirements, correct?

The date field is calling calendar_open from public/javascripts/calendar.js.
To show the calendar, you may try to call calendar_open with the same parameters on a hidden date field. When the user clicks on the date, the calendar should update the hidden field, which can be submitted when the user accepts the form.

Let me know if this works and I’ll be happy to put a link to your investigation.

Handy

Thanks,
Cheri

This post is used mainly for en-us locale. If you use a different locale, you’re correct that ValidatesDateTime.us_date_format = false.

Also, don’t forget to change step 5:
ActiveSupport::CoreExtensions::Date::Conversions::DATE_FORMATS.merge!(:default_date => ‘%m/%d/%Y’)

The default date format for display should be changed as well.

Let me know if you have other question.

Handy

I got all nulls untill I did the following:

ValidatesDateTime.us_date_format = false #use mm/dd/yyyy format

Hey Presto, it worked.

Laters,
j

I installed the plugin as a above, instead of downloading it, and the error has disappeared but there are only nulls being writted to the database. Any ideas?

j

Thanks for the great tutorial. It is really very usefull, however I am getting one error on your implementation. Whne I place ValidatesDateTime.us_date_format = true #use mm/dd/yyyy format in my model I receive the following error:

uninitialized constant Visit::ValidatesDateTime

Have you any ideas, I’m pulling out my hair!

Thanks again.

j

I agree with your comments.

I would like to add that using Rails to maintain database schema helps the developers to eliminate that “one more thing” to do.

Migrations are such a clean way to be able to roll database schemas forward and backward, as well as to be able to tie database schema versions with code versions in the code repository.

Projects that don’t do this will often have the problem where they can restore a past version of the code, but not have any idea what the corresponding database schema was.