Hi Jason,
I've found and fixed this oversight - thanks for bringing it to my
attention (frankly I'm amazed it wasn't found before).
Much as it pains me, I think this warrants a 1.4.1 release :-(
I'll try to do this asap.
Regards, Dave
> -----Original Message-----
> From: Jason Godden [mailto:jasongodden@optushome.com.au]
> Sent: 25 November 2002 07:59
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] PGAdmin schema tracking a bit off...
>
>
> Hi All,
>
> Don't know if anyone else has had this problem (I'm hoping
> someone else has had this problem:)
>
> If I create a second or third schema (PG7.3) in PgAdminII and
> then create a view or table in the new schema and attempt to
> view the data the following message results:
>
> 22/11/2002 07:51:05 - Error in pgAdmin
> II:frmMain.mnuPopupViewData_Click: -2147467259 - ERROR:
> Relation "test" does not exist
>
> Looking at the logs it has executed:
>
> 22/11/2002 07:51:05 - SQL (fsd): SELECT count(*) AS count FROM "test"
>
> When is should have executed:
>
> 22/11/2002 07:51:04 - SQL (fsd): SELECT count(*) AS rows FROM
> sch_parking.test
>
> .. which works fine.
>
> If I use the generic 'public' schema everything is fine...
> (but ofcourse why would I want to use schema's and put
> everthing into public? :)
>
> I have enabled and disabled the auto row count on tables and
> views to no success although I don't know how much effect
> this has (haven't bothered looking at the source code yet...)
>
> This happens regardless of whether it's a view or table. Is
> this a common problem until 7.3 is at release stage? Or does
> the issue lie with PGAdminII? (You guys have done a great
> job of this by the way!) I'm using PGAdminII 1.4 and
> PostgreSQL 7.3 RC1.
>
> Cheers,
>
> Jason
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
http://www.postgresql.org/users-lounge/docs/faq.html