Dave Nation wrote:
> Hi Paul
> 
> Thank you for your reply asking for more info about the problem.

You are most welcome!


> Rather than sending you a rather long program, I made a small program 
> that encapsulated the problem.

Great; this is the preferred way, for a couple key reasons.


> Going through this process enabled me to resolve the problem.

And this is one of those key reasons! :)


> One of the fields in the table was defined as INTEGER DEFAULT '', and a 
> record had been added where the field wasn't specified, and so was given 
> a blank rather than null value.
> SQLite uses manifest rather than static types, and is happy to put a 
> string value in an integer field. Changing the blank entries to NULL 
> entries cured my problem.

Great; thanks for following up.


> It would seem that dabo is not happy with this (strange!) manifest typing.

Dabo is fine with it. It wasn't Dabo that created your field definition 
of INTEGER DEFAULT ''.

For more control setting what field types should be at the Dabo/Python 
level, see dBizobj.DataStructure property:

https://paul.dabodev.com/doc/api/dabodoc/dabo.biz.dBizobj.dBizobj.html#Properties_DataStructure

This wouldn't have solved your specific problem, but I've found 
DataStructure to be indispensable when working with sqlite as well as 
other backends.


> Thanks again for you help, and an excellent framework.

You are welcome!


-- 
pkm ~ http://paulmcnett.com


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]

Reply via email to