Re: pgAdmin bug? snapshot

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin bug? snapshot
Date: 2003-11-19 15:44:52
Message-ID: 03AF4E498C591348A42FC93DEA9661B8720026@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 19 November 2003 15:40
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
>
> Dave Page wrote:
>
> Sounds as if we could enable *all* set variables for this. So
> there would be a database default, user default (both stored
> in the backend), and a query tool default.

Do we really want to _store_ changes made in the query tool? I can just
see ppl forgetting that they changed something in there some time ago
and then not understanding why their query is different in production.

Regards, Dave

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2003-11-19 15:57:37 Re: pgAdmin bug? snapshot
Previous Message Dave Page 2003-11-19 15:42:31 Re: pgAdmin bug? snapshot