System.Data.SQLite

In SQLiteDataReader.VerifyType(int i, DbType typ) DbType.SByte is tested for twice for TypeAffinity.Text:

...
        case TypeAffinity.Text:
-->       if (typ == DbType.SByte) return affinity;
          if (typ == DbType.String) return affinity;
-->       if (typ == DbType.SByte) return affinity;
          if (typ == DbType.Guid) return affinity;
          if (typ == DbType.DateTime) return affinity;
          if (typ == DbType.Decimal) return affinity;
          break;
...

Given that the combination of TypeAffinity.Text and DbType.String is more likely than TypeAffinity.Text and DbType.SByte, I would suggest removing the first test for DbType.SByte. In fact I would probably reorder the tests like this:

        case TypeAffinity.Text:
          if (typ == DbType.String) return affinity;
          if (typ == DbType.DateTime) return affinity;
          if (typ == DbType.Decimal) return affinity;
          if (typ == DbType.Guid) return affinity;
          if (typ == DbType.SByte) return affinity;
          break;

Maybe the other case statements could be optimized too...

Note: This duplicate check has existed since the file was originally added, here:
[0cd344ea4924e4aabe9ee63cd85450c98c0f6ae7].

Also, I'm starting to think that the SByte case should be part of the Int64
affinity.  There is a small risk of breaking compatibility; however, I think
the risk is quite small (i.e. it should be limited to columns that are
explicitly declared with SQL data types that mapped to SByte).

Fixed on trunk via check-in [24b429ba4d].