I have some data that is strictly Integer “1”, “2”, “3”, “4”, or “5”, but a plug-in function that calls for an array of doubles (ChartDirector).
So for tracking that data for use in ChartDirector, should I save the numbers as REAL or INTEGER in an sqlite database? Or does it matter?
Over the years I have often made the assumption that a value would be integer and always integer.
Later, for new functionality I have found myself having to switch to real.
(eg graphics… newer capabilities and PDF export can make use of sub-integer values)
If you are certain these numbers will always be integers, store them that way.
You may not always use Chart Director, and integers are usually faster to work with.
You can always promote them to reals for the function calls.
CDbl() , Floor() and ABS() all do that
And for the record, unlike other databases, SQLite cares very little about the data type of the column.
[quote=338257:@Paul Lefebvre]And for the record, unlike other databases, SQLite cares very little about the data type of the column.
which is sometimes a good thing, and sometimes not so good