Re: relationship to non-class object

• Previous message: Todd O'Bryan: "Re: object regsitered in a different DataContext"
• In reply to: Todd O'Bryan: "Re: relationship to non-class object"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Dec 2, 2005, at 2:25 PM, Todd O'Bryan wrote:

>> Todd,
>>
>> If you schedule is so dynamic that you want it to be data-driven,
>> then it seems like having a separate table for lookup is indeed
>> appropriate. It can be an entity of its own, I see no problem with
>> that.
>
> Should I create a class that just has a Date field, then, with a
> relationship to the day? (Actually, now that I say that out loud,
> it seems like that's probably about the easiest thing to do. Just
> query my DateDay class by date and then getDay() from that.)

This sounds reasonable to me.

Andrus

• Next message: Mike Kienenberger: "Re: object regsitered in a different DataContext"
• Previous message: Todd O'Bryan: "Re: object regsitered in a different DataContext"
• In reply to: Todd O'Bryan: "Re: relationship to non-class object"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Fri Dec 02 2005 - 06:33:29 EST