Good to know...
But why would his ADO be giving back NULL? Unless it has bastardized the sqlite interface? 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. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Jay A. Kreibich [j...@kreibi.ch] Sent: Wednesday, April 18, 2012 10:32 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] "DEFAULT BOOLEAN NOT NULL" not working with entityframework On Wed, Apr 18, 2012 at 01:20:59PM +0000, Black, Michael (IS) scratched on the wall: > default values are during INSERT...not SELECT. > Unless the table has had a column added with ALTER TABLE. In that case, the column doesn't exist in the on-disk record of the row. The SELECT knows it doesn't have enough columns, so it figure out what the default value for that column should be and silently adds it without altering the original record. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
