[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] [INTERFACES] ecpg and the timezone database
From:       "Magnus Hagander" <mha () sollentuna ! net>
Date:       2004-04-30 21:11:51
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B8D7 () algol ! sollentuna ! se
[Download RAW message or body]

>
>Does ecpg need to use the same timezone database as the backend?
>
>I just committed code so it will not, but I am not sure.
>

I think it should not use it, for the following reasons:

* When ecpg is used to write a program, this is a client program. I'd
expect a client program to follow the timezone rules of the client (and
other rules), and not the server. And it has to interface with any
amount of other code that is linked only against the normal timezone
libraries on the client.

* Ecpg is used to write client programs. If it used the "special pg
timezone library", every client program written using ecpg would have to
ship with the pg *timezone database* as well. I'm sure that's now what
you'd want.

But then again, I don't use ecpg myself, so others may certainly have
better arguments in either direction.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

[prev in list] [next in list] [prev in thread] [next in thread]