Alvaro Herrera wrote:
> novnov escribió:
>> I think I get the picture; this post is the closest to making sense to me (my
>> lack of understanding is the issue, obviously). But:
>>
>> What's the postgresql client, in a web app?
>>
>> When you write "The web app sets timezone='EST5EDT' and inserts
On Sep 11, 2007, at 2:48 AM, Gregory Stark wrote:
"Ron Johnson" <[EMAIL PROTECTED]> writes:
On 09/10/07 19:50, Tom Lane wrote:
This whole sub-thread actually is predicated on an assumption not
in evidence, which is that there is any browser anywhere that will
tell the http server timezone i
"Ron Johnson" <[EMAIL PROTECTED]> writes:
> On 09/10/07 19:50, Tom Lane wrote:
>
>> This whole sub-thread actually is predicated on an assumption not
>> in evidence, which is that there is any browser anywhere that will
>> tell the http server timezone information. I'm quite sure no such
>> thing
> > The browser may not know the setting, or may not tell it to you,
> > or you might not be able to make any sense of what it says
> > (timezone names are hardly standardized).
>
> Well that's true. Except for numeric offsets.
Offsets aren't good enough due to changing DST rules. A current
offs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/07 19:50, Tom Lane wrote:
> Ron Johnson <[EMAIL PROTECTED]> writes:
>> On 09/10/07 15:21, Alvaro Herrera wrote:
>>> I wouldn't trust the browser's TZ, and you would need a way to
>>> override it.
>
>> Why?
>
> The browser may not know the se
Ron Johnson <[EMAIL PROTECTED]> writes:
> On 09/10/07 15:21, Alvaro Herrera wrote:
>> I wouldn't trust the browser's TZ, and you would need a way to
>> override it.
> Why?
The browser may not know the setting, or may not tell it to you,
or you might not be able to make any sense of what it says
(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/07 15:21, Alvaro Herrera wrote:
[snip]
>
> I wouldn't trust the browser's TZ, and you would need a way to
> override it.
Why?
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goe
novnov escribió:
>
> I think I get the picture; this post is the closest to making sense to me (my
> lack of understanding is the issue, obviously). But:
>
> What's the postgresql client, in a web app?
>
> When you write "The web app sets timezone='EST5EDT' and inserts a time of
> '2007-07-11 12
On Mon, Sep 10, 2007 at 12:44:04PM -0700, novnov wrote:
> What's the postgresql client, in a web app?
Your webapp *is* the postgresql client. The client is whatever opens
the connection to the server.
> When you write "The web app sets timezone='EST5EDT' and inserts a time of
> '2007-07-11 12:30:
I think I get the picture; this post is the closest to making sense to me (my
lack of understanding is the issue, obviously). But:
What's the postgresql client, in a web app?
When you write "The web app sets timezone='EST5EDT' and inserts a time of
'2007-07-11 12:30:00'." that's the black box th
novnov wrote:
As far as I can see, my original premis is correct, that I need to tweak the
stored datetime when returned for viewing in a browser to adjust for any
user's tz setting...I'd be wrong if browsers automatically adjust any
datetime for the requesting pc's tz setting. I don't think they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/10/07 10:55, Scott Marlowe wrote:
> On 9/10/07, novnov <[EMAIL PROTECTED]> wrote:
>> Your explanation of now() and localtime() is good...but localtime() to
>> postgres acting as a web app db, wouldn't it just return the local time as
>> far as th
On 9/10/07, novnov <[EMAIL PROTECTED]> wrote:
> Your explanation of now() and localtime() is good...but localtime() to
> postgres acting as a web app db, wouldn't it just return the local time as
> far as the server is concerned?
No, it would return it as the local time of the POSTGRESQL client.
On Mon, Sep 10, 2007 at 08:34:55AM -0700, novnov wrote:
> Your explanation of now() and localtime() is good...but localtime() to
> postgres acting as a web app db, wouldn't it just return the local time as
> far as the server is concerned?
It will return localtime relative to whatever you've confi
Martijn van Oosterhout escribió:
> The postgres function now() is the same: it returns a number of seconds.
> Only when you actually go to display it does it do the localtime()
> dance (internally) to make it look nice. That why you can set the
> timezone to whatever you like and everything works
Yes, but there are still some parts of this I don't understand. From the
application user's perspective, the datetime a record was last updated needs
to be presented in their local time, in the browser. I have never been
intimate with web apps that accomodate user profile time settings, but have
u
On Mon, Sep 10, 2007 at 07:46:17AM -0700, novnov wrote:
> But 'apps all know to adjust for TZ'; really? In this case I'm creating the
> app, I can't imagine that it will automatically know to adjust for TZ? The
> postgres function now() would output now as far as the server is concerned
> (per it's
Ha ha that's a funny and accurate way of putting it! I am deploying on a
linux box, so it's good to know this.
But 'apps all know to adjust for TZ'; really? In this case I'm creating the
app, I can't imagine that it will automatically know to adjust for TZ? The
postgres function now() would outpu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/07 22:29, novnov wrote:
[snip]
>
> But it doesn't particularly make sense to set the server's clock to UTC.
> It'd seem to skew a lot of server functionality which I'd think should
> normally be geared around local time. So I'd guess that the
novnov <[EMAIL PROTECTED]> writes:
> At this time my app will be hosted on a server at a single location. Users
> will be updating and viewing from various time zones. I would like to
> present the datetime of the last update to each user according to the time
> zone that they've entered into their
Time zones are a new issue for me. I have read around a bit and learned some.
I have a bunch of questions still because I've not found a really good
overview of how all of the factors tie in together.
At this time my app will be hosted on a server at a single location. Users
will be updating and
21 matches
Mail list logo
