Don't let datestamp fields run into exceptions when submitting out-of-range timestamps

Introduction
The date module enables site users to create so-called datestamp fields,
which use a unix timestamp for storing date values of any entity.
Problem
Currently, the date module doesn't catch the exception when a user enters a date
inside an entity form which can't be represented by the defined integer stamp.
This happens when the date is below the year 1902 or above 2037.

In this case, the user
get an error - or more precisely an exception - message which may look like this:

PDOException: SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column 'field_date_stamp_value2' at row 1: INSERT INTO {field_data_field_date_stamp} (entity_type, entity_id, revision_id, bundle, delta, language, field_date_stamp_value, field_date_stamp_value2) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7); Array ( [:db_insert_placeholder_0] => node [:db_insert_placeholder_1] => 2 [:db_insert_placeholder_2] => 2 [:db_insert_placeholder_3] => article [:db_insert_placeholder_4] => 0 [:db_insert_placeholder_5] => und [:db_insert_placeholder_6] => 1893452460 [:db_insert_placeholder_7] => 2150846145 ) in field_sql_storage_field_storage_write() (line 494 of .../modules/field/modules/field_sql_storage/field_sql_storage.module).

Proposed solution
Catch this exception and show a form error message like "Error on Date #1: The entered date can't be represented by a timestamp. The date must lay between the year 1902 and 2037.".
I think on the Date Field Types documentation should be mentioned that a datestamp module can't handle all dates, only in the mentioned range (although a technical user should be aware of the limits of a unix timestamp).