Zibetti Paolo <[EMAIL PROTECTED]> wrote:
>
> Insert into foo values(5.34);
> Insert into foo values(3.0);
>
> Table foo will contain two rows that both contain a real-type number, so, to
> read the values back from the DB, I can always use sqlite3_column_double().
> With your proposed change it a
Given what I've read so far, you shouldn't have to change any of your code.
Conceptually speaking, all numbers would be
stored as reals internally, though actually some
would be stored as integers if possible for
efficiency.
When you invoke a SQLite accessor function such
as double() or int
Most of the discussion so far was about proposed change number 2, on the
contrary I'm concerned about proposed change number 1.
Does this mean that a number that can be stored as an integer will be stored
as an integer and, thus, I will need to read it back as an integer ?
Here is what I mean: with
3 matches
Mail list logo
