On 19/04/2012 5:14 AM, Jay A. Kreibich wrote:
On Wed, Apr 18, 2012 at 04:09:21PM +0000, Black, Michael (IS) scratched on the
wall:
Good to know...
But why would his ADO be giving back NULL?
Unless it has bastardized the sqlite interface?
That would be my guess.
And I guess that means that if you add a row with a default value then
you should do an "update" afterwords to ensure all the rows are indeed
populated. That may make his ADO happy.
I'm not sure. Since the value is added by the internal logic of
SQLite, in theory there is no difference between a default value from
a newly added column, and if the column actually exists (with the
default value) in the recorded row record. The client shouldn't be
able to tell the difference.
The type "BOOLEAN" will pick up a numeric affinity, but I can't see
that being an issue. Most Boolean values are stored as integer 0 or
1 (in fact, SQLite has optimizations to store integer values 0 and
1 for just this case).
That is interesting to know, I tend to use -1 as true (misspent youth
dabbling in Forth on 8 bit machines).
Regardless, I'd start looking at the ADO code.
-j
--
Regards
John McMahon
li...@jspect.fastmail.fm
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
