| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Alexander Kirpa <pgdoc81(at)bilteks(dot)com> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: Grid editor crash during row insert |
| Date: | 2007-10-15 08:58:14 |
| Message-ID: | 47132BA6.3040007@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Alexander Kirpa wrote:
>> 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.
Oh, you mean the column width? We don't attempt to auto-size the columns
at all, though you can double click a header to make that happen. Any
changes to that code will have to wait until the next development cycle.
> --------------------
> 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.
I can't reproduce this here in SVN trunk, though I did fix a bug that
could easily have caused that a couple of days back. Do you have the
'View System Objects' option turned on so that template0 is visible?
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kirpa | 2007-10-15 12:11:13 | Re: Grid editor crash during row insert |
| Previous Message | Milen A. Radev | 2007-10-14 23:33:26 | Re: Cannot install adminpack |