Re: [pgadmin-support] Grid editor crash during row insert

[Alexander Kirpa]

On 12 Oct 2007, at 17:03, Dave Page wrote:

> > 1. Need retrieve fresh copy of function/trigger function (especially
> > trigger function, each have 2 local copy in PgAdmin DB presentation
> > tree) from server before allow editing - for avoid too annoying
> > message that you see at end editing about old/expired/nonfresh
> > edition of (trigger) function plus chance edit expired function.
>
> Yeah, unfortunately there's no infrastructure to link the two objects
> together at the moment. This was discussed a month or so back.
I speak only about retrieve fresh copy of function body before editing regardless any infrastructure. In other words: before processing 'Properties' at function simulate 'Refresh'
> > 4. Something wrong with 'Limit bar' and 'Database bar' - see garbage
> > under bar during movement left-right
>
> I see a tiny drawing artifact. That's wxWidgets though I believe.
Possible exist way found source of this artifacts?
>
> > 5. Window with already edited function body still no question close
> > in case press 'ESC' :-(
>
> We don't ever query the user if a dialogue is cancelled.
>From user point it is not simple dialog, this is edit function plus during editing PgAdmin track (highlight 'Apply') change function body.
If difficult open 'Yes/no' windows in case already edited body possible simple ignore 'ESC' with (optional) 'Beep'.
>
> > 6. No way determine stripped (partially displayed) or not value in
> > grid result table ('Output pane'->'Data Output') of 'Query' window,
> > for instance try see field name 'i8' type 'bigint' with value
> > '12345678901234567890'. Possible exist reason change 'autoadjust'
> > field width to old behavior (max field value width) or use
> > shift/ctrl sense double click for select behavior.
>
> I don't understand the problem. 12345678901234567890 is out of range
> for a bigint so should never be returned as one. Please provide a self
> contained test case to illustrate the problem.
Sorry. '12345678901234567890' should by '1234567890123456789' for sample only.
I speak about partially visible (or not) field value.

--------------------
Crash again.

Version 1.8.0 RC1 (Oct 9 2007, rev: 6725)
The instruction at "0x0058b778" referenced memory at "0x031cc018". The memory could not be "read".

During expanding DB tree in multi DB servers environment.

Best regards,
Alexander Kirpa