Maybe I'm telling old stories... if so, it's just the case.
I enountered couriosities while working with DOMAINS
When defining an aditional CHECK-constraint, the generated SQL looks like
that:
>
-- Domain: msisdn_type
-- DROP DOMAIN msisdn_type;
CREATE DOMAIN msisdn_type
AS varchar(32)
CHEC
Pgadmin posts an error message and then
stops execution on windows reproducable if you do the
following:
Open a DB,
expand to a
Table
change
Properties,
On Permission page define a SELECT
UPDATE-permission
click
OK
- message
appears
Hi,
maybe I ran into a i18n-Gap or s.t else.
However creating a new operator via GUI-dialog fails because it's impossible
to enter a name for the operator. The text-control seems like it's r/o.
using Pgadmin Jan 14 on Win2k with de_DE l10n
---(end of broadcast)
Hi,
we've got often the problem that we were working on a database just to drop
it afrerwarts and recreate it from the current developement schema. However
postgres denies to drop a DB until all sessions are closed. Since we were
working on it and pgAdmin has no db-specific option (or did we just
>
> Hi,
>
> I'm using pgadmin 1.2.0 the version bundled with postgreSQL 8.0 on a
> windows XP machine. I am unable to enter data on any table if
> that table
> doesn't have a primary key. If the table has a primary key then I can
> enter data through the View edit data screen.
>
You're won
Hi,
I am currently using pg_dump which was delivered with the 14.1.-Version of
PgAdmin III on a 8.0 database.
Issuing the following command:
C:\tools\PGADMI~1>pg_dump.exe -i -h pgv8host -p 5432 -U admin -F p -v
somedb
Results in:
pg_dump.exe: reading schemas
pg_dump.exe: SQL command failed
pg_dum
