Strange exceptions thrown if integer field contains spaces:

Got the following in error.log:

[ Oct 01 2007 17:08:59 ] [192.168.1.66] eZDBInterface::commit TRANSID-94bba195ae7da17f826adfd3b71a4f54:
Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-94bba195ae7da17f826adfd3b71a4f54.
[ Oct 01 2007 17:09:15 ] [192.168.1.66] eZPostgreSQLDB:
Error: error executing query: UPDATE ezcontentobject_attribute
SET language_id='2', contentclassattribute_id='356',
attribute_original_id='0', sort_key_int='301230 ', sort_key_string='',
data_type_string='ezinteger', data_text='', data_int='301230 ', data_float='0.000000'
WHERE id='1616' AND contentobject_id='258' AND version='1' AND language_code='nor-NO' ERROR: invalid input syntax for integer: "301230 "
[ Oct 01 2007 17:09:15 ] [192.168.1.66] eZDBInterface::commit TRANSID-e9e579af834fc7175ab174a68bc9ea27:
Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-e9e579af834fc7175ab174a68bc9ea27.

The solution to this problem would probably be to strip all spaces from integer fields before validating.

Steps to reproduce

Try to create ezobject with an integer field, and type in a space somewhere in the integer e.g '1234 56 78'