On Aug 4, 2:43 pm, Jason Dentler <[email protected]> wrote: > IMO, keeping entities around for the lifetime of the app is bad architecture > regardless of your ORM choice.
Love it when you judge design even before you know what are the requirements ;) How about all kind of dictionaries: list of countries, time zones of the worlds, names of world currencies? How frequently do you want to re-load time zones from DB? At the same time Daylight Time do change from time to time and you can not hardcode it. For some applications, let's say desktop it is perfectly valid assumption that time zone does not change during application life time. Vadim. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
