History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GRAILS-2556
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Graeme Rocher
Reporter: Rick Cromer
Votes: 2
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Grails

Property offeringDate must be a valid Date even if that field allows null

Created: 28/Feb/08 07:23 PM   Updated: 28/Jul/08 08:08 AM
Component/s: Scaffolding
Affects Version/s: 1.0.1
Fix Version/s: 1.0.4

Time Tracking:
Not Specified

File Attachments: 1. Zip Archive dateBug.zip (191 kb)

Environment:
Grails 1.0.1
Win XP SP2
No persistent database
Running from command line
java version "1.6.0_03"
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)


 Description  « Hide
I created a domain with a data field, set the constraints as nullable:true, on the generated create view you can select blanks for dates, but it gives you a validation error.

Property offeringDate must be a valid Date

Project will be attached to this bug.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Goran Ehrsson - 17/May/08 05:06 PM
Same here. Tried with both nullable:true and blank:true. Same error.
Impossible to save a blank/null date.
The created database column allow null.

Goran Ehrsson - 17/May/08 05:20 PM
I added a workaround in my controller that converts blank to null for all dates in the params map. So I'm happy for now.

Steve Tekell - 11/Jun/08 01:38 PM