[pgadmin-support] pgadmin3-20030629-Win32: parse error at or near "as" at character 254

2003-07-01 Thread Jochem van Dieten
I am getting a weird error whenever I expand a table in the tree to show its columns, indexes etc. The error message is "ERROR: parser: parse error at or near "as" at character 254" and is repeated several times. Relevant part of the logfile is attached, but it appears to be a problem in the f

Re: [pgadmin-support] error with domains

2003-01-06 Thread Jochem van Dieten
Dave Page wrote: This should now be fixed. Please update your pgSchema.dll file from the binaries folder on http://cvs.pgadmin.org/. It works now, thanx. Jochem ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an a

[pgadmin-support] error with domains

2003-01-04 Thread Jochem van Dieten
After creating a new schema and a domain in it, pgAdmin is unable to display the schema. The code used to create the schema in psql: jochemd=> select version(); version - PostgreSQL 7.3.1 on i386-un

Re: [pgadmin-support] altering the name of the public schema [SOLVED]

2002-12-02 Thread Jochem van Dieten
Dave Page wrote: From: Jochem van Dieten [mailto:[EMAIL PROTECTED]] Could it be that somewhere in pgAdminII there is a reference to the OID 2200 that is assigned to the public schema by default? pgAdmin hides system objects by default, but in the case of the public schema it makes an

[pgadmin-support] altering the name of the public schema

2002-12-01 Thread Jochem van Dieten
[restarting the "Renaming schema's" thread from pgsql-general] Using pgAdminII version 1.4.2 with PostgreSQL 7.3 I can alter the name of a schema using: test=# update pg_catalog.pg_namespace test-# set nspname = 'newname' test-# where nspname = 'oldname'; This works without a problem unt