Re: attribute's serverTimeZone
Re: attribute's serverTimeZone
- Subject: Re: attribute's serverTimeZone
- From: Mike Schrag <email@hidden>
- Date: Thu, 23 Oct 2008 20:25:28 -0400
It's documented as being implemented in the EOAdaptorChannel
Although I understand your logic, would it be better to ask Apple to
correct the fact that it does not work rather than put it into the
adaptor. TimeZones are just fine as long as it's switching from GMT
at the 'view layer', but if one ends up with multiple points of
timezone offsetting in the pipeline between the database and the
view layer, it really does become baffling! If you put support for
it into the Wonder adaptors then Apple fix it in the adaptor
channel, this situation may arise in the future.
I would add a toggle for this, defaulting off (for backwards
compatibility). As far as asking Apple to correct it, I can't really
depend on Apple fixing things that I need to solve in real life now.
Sure, I can log a bug, but when am I going to see that in a release?
If they choose to care about my request, which they might not, maybe
it will make into the next beta that maybe will be available at WWDC
in 8 months and in a real release in what, a year? For better or
worse, this is why we take the approach we do with Wonder. We muck
with lots of things, but if you have the problem, we can solve it now
vs waiting for Apple to maybe solve ... eventually. Pierre may hate
us for it, but clients trump politics for me any day.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden