Skip site navigation (1) Skip section navigation (2)

Re: ecpg and the timezone database

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>,"PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>,"PostgreSQL-interfaces" <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: ecpg and the timezone database
Date: 2004-04-30 21:11:51
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B8D7@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
>
>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

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2004-04-30 23:05:35
Subject: Re: ecpg and the timezone database
Previous:From: Andrew SullivanDate: 2004-04-30 21:04:44
Subject: Re: Call for 7.5 feature completion

pgsql-interfaces by date

Next:From: Andrew DunstanDate: 2004-04-30 23:05:35
Subject: Re: ecpg and the timezone database
Previous:From: Bruce MomjianDate: 2004-04-30 20:48:33
Subject: ecpg and the timezone database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group