System.Data.SQLite

The field type is BOOLEAN, the value of the field is "t" or "f".  When calling System.Data.SQLite.SQLiteConvert.ToBoolean("f"), a System.ArgumentException is called.  This is called when utilizing a SQLiteDataReader class to access the field.

relevant stack:

System.ArgumentException was unhandled
  HResult=-2147024809
  Message=source
  Source=System.Data.SQLite
  StackTrace:
       at System.Data.SQLite.SQLiteConvert.ToBoolean(String source)
       at System.Data.SQLite.SQLiteConvert.ToBoolean(Object obj, IFormatProvider provider, Boolean viaFramework)
       at System.Data.SQLite.SQLite3.GetBoolean(SQLiteStatement stmt, Int32 index)
       at System.Data.SQLite.SQLite3.GetValue(SQLiteStatement stmt, SQLiteConnectionFlags flags, Int32 index, SQLiteType typ)
       at System.Data.SQLite.SQLiteDataReader.GetValue(Int32 i)
       at System.Data.SQLite.SQLiteDataReader.get_Item(String name)

Normally, the BOOLEAN type requires the string to be "true" or "false", not just
"t" or "f".  Did a previous version of System.Data.SQLite used to support using
just the strings "t" or "f" in this context?

Apparently, the previous versions silently treated all invalid BOOLEAN values as
"false" and now an exception is thrown instead.

The values "t" and "f" were never really supported as "BOOLEAN", per se;
however, the exception behavior was changed (inadvertently) in release
1.0.99.0.

That being said, I think the new behavior is more correct.

I'm adding code to trunk that will allow BOOLEAN values to be recognized if
they are any valid case-insensitive prefix of "True" and "False", including
"t" and "f".

This has been "fixed" on trunk via check-in [ecf9a72b79755c26].