That obviously works. I also thought that the FC team had a default datetime that was something like 100 years in the future as a 'null' datetime... I don't know why it wouldn't take null though.
Tomek On Tue, May 26, 2009 at 3:26 AM, Michael Sharman <[email protected]> wrote: > > Adding an actual defualt value seems to fix: > > default="1900-01-01 00:00:00" > > Ideally if the value wasn't required, NULL would be used instead. > > > On May 26, 4:37 pm, Michael Sharman <[email protected]> wrote: > > Hi guys, > > > > I've run into this problem before but thought I'd post here to see if > > others are having the same issues. > > > > I have an existing object type but want to add a new property which > > happens to be a date, no matter what I do I get an error because I > > believe the default value ('') is incorrect. I assume the coapi is > > trying to make the default value an empty string in the SQL and as the > > datatype is a datetime it is of course failing. > > > > This is my cfproperty (molded off dmHTML.cfc): > > > > <cfproperty ftSeq="2" ftFieldset="Basic Details" name="EventStartDate" > > type="date" ftType="datetime" required="false" default="" > > ftLabel="Start Date"> > > > > Note that I've tried removing the default="" attribute but got the > > same error. > > > > Any ideas before I post a bug report? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
