On Tuesday 14 March 2006 13:27, Michael Van Canneyt wrote:
> On Tue, 14 Mar 2006, johnf wrote:
> > On Tuesday 14 March 2006 11:07, Jesus Reyes wrote:
> > > --- johnf <[EMAIL PROTECTED]> escribió:
> > > > Hi I am now attempt to populate a dbgrid with the data I get from
> > > > my
> > > > sqlquery1. As I scroll across the columns I get the following:
> > > >
> > > >
> > > > Am I doing something wrong or is this another bug?????
> > > >
> > > > John
> > >
> > > The grid is trying to paint some field content, and maybe not all
> > > types of fields are ready implemented in the postgress dataset part?.
> > >
> > > To know what field is causing problem, try to add some columns to a
> > > "live" grid, then try to change the field name of the column, if that
> > > fails you have found the culprit field, checkout how is defined in
> > > you database, what is your sql statement?
> > >
> > > Jesus Reyes A.
> >
> > I have updated the FPC to 2.1.1 and Lazarus to .13. and now get a
> > different error message:
> > TGtk2WSCustomListBox.SetBorder TODO
> > TApplication.HandleException Fieldtype Blob is not supported
>
> [cut]
>
> > (ptrymysql:24220): GLib-GObject-WARNING **: gsignal.c:1788: instance
> > `0x846fce8 has no handler with id `449'
> > [TGtkWidgetSet.Destroy] WARNING: There are 1 unreleased DCs, a detailed
> > dump fo lows:
> > [TGtkWidgetSet.Destroy] DCs: 4001F0F8
> > [TGtkWidgetSet.Destroy] WARNING: There are 6 unreleased GDIObjects, a
> > detailed ump follows:
> > [TGtkWidgetSet.Destroy] GDIOs: 40960868 409626A8 40962668 4095F468
> > 4095F1A8 4 95F4A8
> > [TGtkWidgetSet.Destroy] gdiBitmap: 3
> > [TGtkWidgetSet.Destroy] gdiBrush: 1
> > [TGtkWidgetSet.Destroy] gdiFont: 1
> > [TGtkWidgetSet.Destroy] gdiPen: 1
> >
> > I hope someone can figure this out. BTW my table has not blob data type
> > in it. The error occurs at about the same area.
>
> Nevertheless the error seems to point in that direction.
> Does it have a memo field ? (i.e. unlimited text field ?)
>
> if so, you can't show that in a grid.
>
> Michael.
I don't see one. So I added one (actually a text field) and got the same
error but removing the blob/text field still produces the error. I'm using
postgres 7.4.8. I have created a new table (test) with only Varchar fields
and it works correctly. I'm checking to see if adding more columns of
numeric have anything to do with the error message.
John
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives