It's the keyboard -- just got a new MS keyboard at work and didn't
notice it has an 'F Lock' key at the top, near Scroll Lock. I must
have hit wit inadvertently, and thereby disabled the F keys.
The F lock is the single most annoying keyboard development EVER. And I
thought over the last few
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 08 February 2004 23:01
> To: Steve Fox
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] F2 key not working for editing
> rows on XP
>
>
> These M$ induced keyboard layout changes are a PITA. The US
Hi,
Could you unsubscribe me with this account ?
and send for another account [EMAIL PROTECTED]
Regards
Tien
Dave Page wrote:
>
>
>
> > -Original Message-
> > From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> > Sent: 08 February 2004 23:01
> > To: Steve Fox
> > Cc: [EMAIL PROTECTED]
>
Andreas Pflug wrote:
>> I have PgAdmin III 1.0.2 and PostgreSQL 7.4.1.
>> When I create a table with primary key constraint on it, PostgreSQL
>> automatically creates an index on that column (or columns), which is
>> then shown in psql with \di command.
>> But PgAdmin does not show that index in
>>
> -Original Message-
> From: Constantin Stefanov [mailto:[EMAIL PROTECTED]
> Sent: 09 February 2004 09:03
> To: Andreas Pflug
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Indexes generated for primary
> key are not show
>
> Why should such duplication be avoided? There is
Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 08 February 2004 23:01
To: Steve Fox
Cc: [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] F2 key not working for editing
rows on XP
These M$ induced keyboard layout changes are a PITA. The US
d
Dave Page wrote:
>>Why should such duplication be avoided? There is both
>>constraint (primary key) and index.
>
> Because if any generated SQL contains both object, it will be an invalid
> script, not to mention the fact that you cannot properly recreate
> constraints just by recreating the in
> -Original Message-
> From: Constantin Stefanov [mailto:[EMAIL PROTECTED]
> Sent: 09 February 2004 10:25
> To: Dave Page
> Cc: Andreas Pflug; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Indexes generated for primary
> key are not show
>
> Well, I did not think you were talking
Dave Page wrote:
> The primary question remains though, why should we expose implementation
> details of something like a primary key when we already show the primary
> key itself? It's not like you cannot see the columns in it or anything.
> Should we by the same argument show the triggers that i
> -Original Message-
> From: Constantin Stefanov [mailto:[EMAIL PROTECTED]
> Sent: 09 February 2004 12:54
> To: Dave Page
> Cc: Andreas Pflug; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] Indexes generated for primary
> key are not show
>
> I think at least to have an option (ma
Constantin Stefanov wrote:
As for quick solution I would suggest checking with psql - if it can
shows something, then PgAdmin should have an option to show it. I think
many people use psql and it has almost all features needed for working
with PostgreSQL (but it is less convenient than PgAdmin). A
11 matches
Mail list logo