> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> Alexey Vorobyev
> Sent: 19 January 2006 02:44
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] Pgadmin III not honoring DATESTYLE
>
> I Don't think it's a good idea to set it's own Datestyle in pgAdmin.
> I work both witg psql and pgAdmin and have "German" datestyle
> set for database.

Psql doesn't have to deal with multiple connections to different
databases, let alone different servers at once. Having had to fix the
end result of the confusion that differing datestyles can cause on a
multi-million row table there is no way I'd want pgAdmin to work in
anything other than unambiguous ISO format.

> It's not very easy to switch my mind between datestyles.

Well, I would consider applying a patch that gave the user the option of
turning on database-formatted dates, but only if it was off by default.
This is not something I'm going to work on though.

> By the way, previous versions of pgadmin (II ?) worked well.

pgAdmin II was an entirely different application written using different
technology with it's own set of problems. It certainly suffered from the
ambiguity problem that is my main concern, although to a lesser extent
as it only connected to one server at a time.

Regards, Dave.

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