Shhh, didn't think of that. So we won't ever accept unique indices for
this.
What we do in phpPgAdmin is that rows with NULL values in the unique key
simply aren't editable - all other rows are though.
In order, we prefer to use a PK (since it is indexed), then oid column
(since it is complete)
Markus Wollny wrote:
I think I found out what's causing the connection dropping - it's not
really the firewall, it's the dynamic NAT routing. Our admin doesn't
want to set up static NAT routing for the developers though if he can
help it - he says that this should be reserved for servers.
Huh,
I think I found out what's causing the connection dropping - it's not
really the firewall, it's the dynamic NAT routing. Our admin doesn't
want to set up static NAT routing for the developers though if he can
help it - he says that this should be reserved for servers.
As an easy solution to the
pgAdmin III does not appear to handle passwords with spaces in them.
Leading and trailing spaces simply fail to authenticate.
Internal spaces produce the error message:
missing '=' after 'xxx' in connection info string
Where 'xxx' is the part of the password after the space.
For refer
I am not sure of your exact situation, but I am using a windows client with
putty setting up an SSH tunnel to get through the
firewall, one of the options on putty allows you to set a keep alive message
every XX seconds. I have kept this connection
up for days without problems...
Jim
---
Hi,
This error normally occurs because the backend database
doesn't like the style of number you are using. Try entering '-591.87'
instead.
Regards Dave.
From: Robson Richieri
[mailto:[EMAIL PROTECTED] Sent: 18 February 2004
14:46To: [EMAIL PROTECTED]Subject:
[pgadmin-sup
-- System Information --Platform: Windows 2000Version:
5.0Build: 2195 Service Pack 2-- Application Information
--Name: pgAdmin IIVersion: 1.6.0Descripton: Name:
pgSchemaVersion: 1.6.0Descripton: PostgreSQL Schema Objects
v1.6.0-- Database Information --Version: 7.2.1Descripton:
PostgreSQL
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 18 February 2004 10:13
> To: Christopher Kings-Lynne
> Cc: [EMAIL PROTECTED]; [pgADMIN]
> Subject: Re: [pgadmin-support] inserting new records without OIDs
>
> Christopher Kings-Lynne wrote:
>
> >> Not true.
Christopher Kings-Lynne wrote:
Not true. Currently, you need either OID *or* a primary key.
Obviously, that id column should get a pk.
We'll extend the grid some time, to accept any other unique keys
also. Still, defining a PK on every table is best practice.
Defining a column as serial does *no
