On Jun 11, 2009, at 9:14 PM, dbcor...@rockwellcollins.com wrote: > I receive erroneous data when I try to populate a table using data > from > another table: Here is how! > > I have TABLE A (that has IDs of INTEGER, Seats as INTEGER, and so > forth) > > I want to take this master table and in essence transfer the data I > only > need into > another table called TABLE B (say it only has IDs of INTEGER) > > To do this I do the following > INSERT INTO TABLE B SELECT DISTINCT Content_ID from TABLE A > > unfortunately numbers like > > 854459, 854477, > 900499, 900517, > 905209, 905227, > > will produce float results of 854459.000000001, 854477.000000001, etc. > but the neighboring numbers stay intact and do not produce a float > value.
Impossible. SQLite never converts an integer into a float without a very good reason (such as the number is too large to represent as an integer, or there was an explicit cast). Unless, of course, you are using a really, really old version of SQLite, like version 2.8 or something. Can you provide a test case that shows an integer being converted into a floating point value? D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
