Re: Core Data date defaults
Re: Core Data date defaults
- Subject: Re: Core Data date defaults
- From: John Timmer <email@hidden>
- Date: Thu, 09 Jun 2005 12:38:56 -0400
> In a data model, if you create an entity with a Date attribute, is
> there a way to specify it to default to the current date and time
> without subclassing NSManagedObject? Is there a system variable or
> something you can put in the default field that will do this? The
> documentation is mum on this point, but it seems like there's little
> reason to have a default value field on Date entities if you can't do
> that.
I can't answer your question, but I can tell you that there is some value to
having a default date. It turns out that Core Data can't handle a nil date
properly - it treats nil as a time interval, and so a nil date winds up
looking like 1970. If a date in 1970 is valid from your application's
perspective, then nil dates become a serious problem, which you can solve by
making a default date be an invalid one, something like December 30th, 1899.
JT
_______________________________________________
This mind intentionally left blank
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden