Author: aklaver@comcast.net (Adrian Klaver)
Posted: 2008-02-10 13:18:22 Link
I changed to the svn version of Dabo(3910). The Editable property still does not persist but I do not get a core dump. Instead I get the following error message at the point where it used to dump.
Dabo Error Log: Sun Feb 10 10:09:13 2008: !!! Data Type Mismatch: field=qty. Expecting: <class 'decimal.Decimal'>; got: <type 'unicode'>
The field 'qty' is Numeric in the Postgres table. Is there a way to tell Dabo the value entered is a Decimal?
--
Adrian Klaver
aklaver@comcast.net
Author: aklaver@comcast.net (Adrian Klaver)
Posted: 2008-02-10 13:34:58 Link
-------------- Original message ----------------------
From: aklaver@comcast.net (Adrian Klaver)
> I changed to the svn version of Dabo(3910). The Editable property still does not
> persist but I do not get a core dump. Instead I get the following error message
> at the point where it used to dump.
> Dabo Error Log: Sun Feb 10 10:09:13 2008: !!! Data Type Mismatch: field=qty.
> Expecting: <class 'decimal.Decimal'>; got: <type 'unicode'>
> The field 'qty' is Numeric in the Postgres table. Is there a way to tell Dabo
> the value entered is a Decimal?
>
> --
> Adrian Klaver
Forgot to add that in spite of the dGrid Editable not being set True and the type error the field value was changed and updated.
--
Adrian Klaver
aklaver@comcast.net
On Feb 10, 2008, at 12:18 PM, Adrian Klaver wrote:
> I changed to the svn version of Dabo(3910). The Editable property
> still does not persist but I do not get a core dump.
I guess you could call that progress. ;-)
I still haven't had the time to track that down. I started working on
it, and confirmed that the property is being set correctly by the
Class Designer, but is then reverted at some point. I haven't been
able to find what is causing it to revert to Editable=False.
> Instead I get the following error message at the point where it used
> to dump.
> Dabo Error Log: Sun Feb 10 10:09:13 2008: !!! Data Type Mismatch:
> field=qty. Expecting: <class 'decimal.Decimal'>; got: <type 'unicode'>
> The field 'qty' is Numeric in the Postgres table. Is there a way to
> tell Dabo the value entered is a Decimal?
Numerics should be represented inside of Dabo by Decimal if you have
the Decimal module available, or float if you do not. Since you are
running Python 2.5.1, you should have Decimal available to you.
Also, it seems Dabo is aware of the type, as it says that it is
expecting a decimal, but didn't get one. At what point does this
message appear?
-- Ed Leafe
On Sunday 10 February 2008 11:13:43 am Ed Leafe wrote:
> > Instead I get the following error message at the point where it used
> > to dump.
> > Dabo Error Log: Sun Feb 10 10:09:13 2008: !!! Data Type Mismatch:
> > field=qty. Expecting: <class 'decimal.Decimal'>; got: <type 'unicode'>
> > The field 'qty' is Numeric in the Postgres table. Is there a way to
> > tell Dabo the value entered is a Decimal?
>
> Numerics should be represented inside of Dabo by Decimal if you have
> the Decimal module available, or float if you do not. Since you are
> running Python 2.5.1, you should have Decimal available to you.
>
> Also, it seems Dabo is aware of the type, as it says that it is
> expecting a decimal, but didn't get one. At what point does this
> message appear?
>
> -- Ed Leafe
Is this a ClassDesigner issue? I ask because I don't see this happening with
my grids.
--
John Fabiani
On Feb 10, 2008, at 2:09 PM, johnf wrote:
> Is this a ClassDesigner issue? I ask because I don't see this
> happening with
> my grids.
Yes. The Class Designer sets the Editable property as saved, but then
something re-sets it to False.
-- Ed Leafe
On Sunday 10 February 2008 11:13 am, Ed Leafe wrote:
> On Feb 10, 2008, at 12:18 PM, Adrian Klaver wrote:
> > I changed to the svn version of Dabo(3910). The Editable property
> > still does not persist but I do not get a core dump.
>
> I guess you could call that progress. ;-)
>
> I still haven't had the time to track that down. I started working on
> it, and confirmed that the property is being set correctly by the
> Class Designer, but is then reverted at some point. I haven't been
> able to find what is causing it to revert to Editable=False.
The strange part is that even though Editable!=True I can edit the column in
the grid and the value is saved to the database.
>
> > Instead I get the following error message at the point where it used
> > to dump.
> > Dabo Error Log: Sun Feb 10 10:09:13 2008: !!! Data Type Mismatch:
> > field=qty. Expecting: <class 'decimal.Decimal'>; got: <type 'unicode'>
> > The field 'qty' is Numeric in the Postgres table. Is there a way to
> > tell Dabo the value entered is a Decimal?
>
> Numerics should be represented inside of Dabo by Decimal if you have
> the Decimal module available, or float if you do not. Since you are
> running Python 2.5.1, you should have Decimal available to you.
>
> Also, it seems Dabo is aware of the type, as it says that it is
> expecting a decimal, but didn't get one. At what point does this
> message appear?
It appears after I enter the value in a grid column and tab to the next
column. To answer Johns question, this is in a ClassDesigner form created by
clicking on Run in the CD File menu.
>
> -- Ed Leafe
>
>
>
>
>
[excessive quoting removed by server]
On Feb 10, 2008, at 1:13 PM, Ed Leafe wrote:
> I still haven't had the time to track that down. I started working on
> it, and confirmed that the property is being set correctly by the
> Class Designer, but is then reverted at some point. I haven't been
> able to find what is causing it to revert to Editable=False.
OK, I finally tracked it down and fixed it. The changes have been
committed to svn and Web Update.
-- Ed Leafe
On Sunday 10 February 2008 7:00 pm, Ed Leafe wrote:
> On Feb 10, 2008, at 1:13 PM, Ed Leafe wrote:
> > I still haven't had the time to track that down. I started working on
> > it, and confirmed that the property is being set correctly by the
> > Class Designer, but is then reverted at some point. I haven't been
> > able to find what is causing it to revert to Editable=False.
>
> OK, I finally tracked it down and fixed it. The changes have been
> committed to svn and Web Update.
>
> -- Ed Leafe
>
Tried it out and it works.
Thanks,
--
Adrian Klaver
aklaver@comcast.net