Typing non-digits into default traffic flow fields errors out

What steps will reproduce the problem?
1. Enter non-digit characters in a default traffic flow
2. Click save

What is the expected output? What do you see instead?
- We expect a nice error message
- A server error occured, check logs

Log information:

UPDATE defaulttrafficflow SET w2wk = aa, w2sa = null, w2sh = null, w3wk = null, 
w3sa = null, w3sh = null, pcwk = null, pcsa = null, pcsh = null, txwk = null, 
txsa = null, txsh = null, ldvwk = null, ldvsa = null, ldvsh = null, ldcwk = 
null, ldcsa = null, ldcsh = null, hdcwk = null, hdcsa = null, hdcsh = null, 
mdbwk = null, mdbsa = null, mdbsh = null, hdbwk = null, hdbsa = null, hdbsh = 
null WHERE id = '0970f9db-8822-4935-90ae-999728d24021'

Note the value for w2wk = aa, where aa is supposed to be an integer. However, 
as a string it is not within single quotes, so postgres thinks it is a column 
in the database.

The RegioBO handling the save should validate all the numeric fields and 
present a nice error to the user.

Original issue reported on code.google.com by stuartmo...@gmail.com on 19 Aug 2010 at 2:52

lijian8 / tamt

Typing non-digits into default traffic flow fields errors out #30