On Wed, 25 Jul 2012 11:05:27 +0200, Dimitry Sibiryakov <[email protected]> wrote: > 25.07.2012 10:59, arnaud but wrote: >> i know but the problem is in an INSERT statement (on thi table) after >> the prepare the sqltype of this comlums is 448 (base10) so sqltype & 1 >> == 0 maybe it's normal. > > It is NOT normal. And I suspect, that this is result of YOUR database > corruption. > Show us table description and SQLDA dump from isql to avoid possible Qt > problems.
Maybe I have things confused regarding column nullability. But I thought this check indicates if the column is nullable (sqltype & 1 == 1) or not nullable (sqltype & 1 == 0), a primary key is by definition not nullable, so the behavior described is IMHO expected. Maybe this changed between 2.1 and 2.5. I am not sure why this would be attributable to "YOUR database corruption". Mark ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
