> -----Original Message-----
> From: Sven Köhler [mailto:skoehler@upb.de]
> Sent: 19 June 2003 17:17
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] pgAdmin III
>
>
> > Just wanted to know if you wanted reports back about bugs
> in pgAdmin
> > III. I haven't seen any been reported or may be I just missed them?
>
> So i should add one:
> If i try to view a table with pgAdminIII (by klicking on the
> sunglasses
> or by doing a "select *" in the SQL window) pgAdmin crashes.
> The crash is caused a memory access violation.
Very odd. I'm using it in preference to pgAdmin II in production now and finding 200,000 row tables barely make it
blink.Is it a specific table, or schema? Also, are there any potential trouble-making columns in your tables such as
blobsor byte arrays?
> I'm using WinXP with postgresql under cygwin.
> My DB is a Unicode DB, although i think, that it used to
> happen with an
> ASCII DB to.
>
> I tested http://www.pgadmin.org/snapshots/pgadmin3-Alpha-Win32.zip
> and http://www.pgadmin.org/snapshots/win32/pgadmin3-20030619-Win32.zip
>
> Both version crash :-(
>
> BTW:
> Does pgAdmin use the ODBC driver anymore? or is are client
> libs compiled
> in statically?
pgAdmin III has two classes pgConn and pgSet which which roughly emulate the MDAC functionality that pgAdmin II used.
Theseclasses make use of libpq (statically linked on Windows), not ODBC (this is mainly why the query engine is so much
betternow performance wise).
Regards, Dave.