Re: Solved: Default value for Date Atttribute in Core Data application

FROM : Lee Gillen
DATE : Sun Aug 13 20:14:00 2006

Yes, using "now" and "today" give the same result. Both produce an 
NSDate with the date set to the current date and the time set to 12 
pm for the the current time zone. I think that result is appropriate 
for "today" but it is not for "now". "Now" should designate the 
current date *and* time. IMHO at least.

Robert Cerny correctly stated that using awakeFromInsert is the 
appropriate place to use [NSDate date] as you suggested. I ended up 
with the following in my NSManagedObject subclass.

- (void)awakeFromInsert
{
   [super awakeFromInsert];
   [self setValue:[NSDate date] forKey:@"dateCreated"];
}

While this is very simple, if "Now" included the current date and 
time I would not have had to subclass and add this method.

Thank you Bill and Robert for your help.

Lee

On Aug 12, 2006, at 8/12/06 8:21 PM, Bill Coleman wrote:

>
> On Aug 10, 2006, at 9:18 AM, Lee Gillen wrote:
>

>> I have a Core Data application that has a date attribute for one of
>> the entities. I'd like to set the default value for this attribute to
>> be the current date and time that the data was created. I found 
>> that I
>> can use a default value of 'now' or 'today' and it will populate the
>> attribute with the date the data was created, but not the time.

>
> I couldn't do this with a default value -- ran into the same 
> problem, "TODAY" produces a time of 12 noon.
>
> What I did was set the time to [NSDate date] in code after creating 
> the object.
>
> Bill Coleman, AA4LR, PP-ASEL        Mail: <email_removed>
> Quote: "We invented personal computing."
>            -- Bill Gates @ TechNet / MSDN 2003
>
>