On 18 Apr 2012, at 1:54pm, Steffen Mangold <steffen.mang...@balticsd.de> wrote:
>> I think your problem is with the ado provider. Perhaps it makes the >> assumption that every value in a BOOLEAN column must be a BOOLEAN. This is >> not true under SQLite: you can have any value in a BOOLEAN column, even TEXT. > > Hi Simon, > > Yes correct because if you alter a table with a new BOOLEAN column with a > default value, all existing row still have NULL as value. There's no way to alter an existing column in SQLite. You can rename or add a column, but not change a column definition. If your application makes you think it's changing a column definition, and that's not working properly, the bug is in the application. > I think in a correct way the ado provider has to return the default (in my > case 0 = false) value if field is NULL and not throw these error. > > I think this is a bug. Do you with me? It's not a bug in SQLite. It might be a bug in the ADO or the application you're using, but those aren't written by the SQLite team, so you can't blame the bug on SQLite. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
