I think I have pinned down a situation which reliably crashes the
1. Open a database and select a table in the tree view
2. Click the pencil icon to edit the underlying SQL
3. Execute the SQL. You obviously get an error that the table already
exists, since the 'drop table' is commented out.
4. Close the window, and select no when asked if you want to save.
Just tried this on the new Debian box, with the same result.
Hope this is useful.
On Thu, 2004-02-26 at 17:37, Andreas Pflug wrote:
> Tim Booth wrote:
> >I love PGAdminIII, and use it extensively on my Redhat Linux box. I'm
> >currently using a CVS build as it fixes a significant crashing situation
> >over the stable release. However, I find the disappearence of the
> >cursor/caret in the SQL editor very annoying.
> Hi Tim,
> can you tell us in which situation stable (1.0.2?) crashes? Seems we
> missed to backport a fix.
In response to
pgadmin-hackers by date
|Next:||From: Rainer Lay||Date: 2004-02-27 14:54:07|
|Subject: padmin3 and SuSE 9.0|
|Previous:||From: Hiroshi Saito||Date: 2004-02-26 17:43:44|
|Subject: Re: Solaris9 Sparc64 edition|