Dave Page a écrit :
On Wed, Jun 11, 2008 at 9:06 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
Hmm, good point. The original intent behind the feature was for
teaching environments in which there may be one database for each
student, so the students could limit their list to just their own
da
On Wed, Jun 11, 2008 at 9:06 AM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
>> Hmm, good point. The original intent behind the feature was for
>> teaching environments in which there may be one database for each
>> student, so the students could limit their list to just their own
>> database with
Dave Page a écrit :
On Fri, Jun 6, 2008 at 3:22 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
Dave, what do you think I should do ? remove the patch ?
Just remove the NOT?
I can do this. But, for example, if someone was using this filter field to
get out template databases, removing the N
ely,
Zach Conrad
- Original Message -
From: "Dave Page" <[EMAIL PROTECTED]>
To: "Guillaume Lelarge" <[EMAIL PROTECTED]>
Cc: "Zach Conrad" <[EMAIL PROTECTED]>, pgadmin-support@postgresql.org
Sent: Friday, June 6, 2008 9:26:57 AM GMT -06:00 US/
On Fri, Jun 6, 2008 at 3:22 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
>>> Dave, what do you think I should do ? remove the patch ?
>>
>> Just remove the NOT?
>>
>
> I can do this. But, for example, if someone was using this filter field to
> get out template databases, removing the NOT won'
Dave Page a écrit :
On Fri, Jun 6, 2008 at 3:12 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
Zach Conrad a écrit :
Thank you for your quick response.
There are a few things this brings up:
1. The pgAdmin help file states the use of datname IN ('blah') in the DB
Restriction field
2. Most p
On Fri, Jun 6, 2008 at 3:12 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
> Zach Conrad a écrit :
>>
>> Thank you for your quick response.
>>
>> There are a few things this brings up:
>>
>> 1. The pgAdmin help file states the use of datname IN ('blah') in the DB
>> Restriction field
>> 2. Most p
Zach Conrad a écrit :
Thank you for your quick response.
There are a few things this brings up:
1. The pgAdmin help file states the use of datname IN ('blah') in the DB
Restriction field
2. Most people know which databases they want to connect to. Wouldn't it make
more sense to use datename
essage -
> From: "Guillaume Lelarge" <[EMAIL PROTECTED]>
> To: "Zach Conrad" <[EMAIL PROTECTED]>
> Cc: pgadmin-support@postgresql.org
> Sent: Thursday, June 5, 2008 3:31:55 PM GMT -06:00 US/Canada Central
> Subject: Re: [pgadmin-support] 1.8.4 bug DB Res
5, 2008 3:31:55 PM GMT -06:00 US/Canada Central
Subject: Re: [pgadmin-support] 1.8.4 bug DB Restriction field
Zach Conrad a écrit :
> DB Restriction field borks on datname IN ('blah') or datname='blah' with the
> error: "ERROR: operator does not exist: name <>
Zach Conrad a écrit :
DB Restriction field borks on datname IN ('blah') or datname='blah' with the error:
"ERROR: operator does not exist: name <> boolean LINE 5: WHERE datname NOT IN
(datname='blah')
Here's the full query from the logs being sent from pgAdmin:
SELECT db.oid, datname, db.dat
DB Restriction field borks on datname IN ('blah') or datname='blah' with the
error: "ERROR: operator does not exist: name <> boolean LINE 5: WHERE datname
NOT IN (datname='blah')
Here's the full query from the logs being sent from pgAdmin:
SELECT db.oid, datname, db.dattablespace AS spcoid, sp
12 matches
Mail list logo
