Hi Simon,
>
> So you can declare a column as INTEGER and supply the string '1234'
> and it will be converted to the number 1234 before it is stored. You
> can check this out using
>
> SELECT x,typeof(x) FROM myTable
>
> This means that the conversion is done once on storage rather than
> each
On 2015-08-27 04:06 PM, Nicolas J?ger wrote:
> Hi Darko, Igor and others.
>
>so the only reason to define datatype in sqlite is for the size on
>the disk ?
>
>so why not just only using `BLOB` (excepted for `INTEGER PRIMARY
>KEY`) ?
>
>being less persmissive wouldn't make
On 27 Aug 2015, at 3:06pm, Nicolas J?ger wrote:
> so the only reason to define datatype in sqlite is for the size on
> the disk ?
Nope. It has no effect on the size on disk.
> so why not just only using `BLOB` (excepted for `INTEGER PRIMARY
> KEY`) ?
>
> being less persmissive wouldn't
. August 2015 16:07
An: sqlite-users at mailinglists.sqlite.org
Betreff: Re: [sqlite] why I don't get an error ?
Hi Darko, Igor and others.
so the only reason to define datatype in sqlite is for the size on
the disk ?
so why not just only using `BLOB` (excepted for `INTEGER PRIMARY
KEY
ok, thx everyone!
especially R. Smith
regards,
Nicolas
On 8/27/2015 10:06 AM, Nicolas J?ger wrote:
>so the only reason to define datatype in sqlite is for the size on
>the disk ?
I don't quite see how size on disk has anything to do with it.
The main reason to define the column data type is to establish column
affinity.
>so why not
Hi Darko, Igor and others.
so the only reason to define datatype in sqlite is for the size on
the disk ?
so why not just only using `BLOB` (excepted for `INTEGER PRIMARY
KEY`) ?
being less persmissive wouldn't make querries run faster ?
for example, the comparisons would not have to
SQLite records have fields that are variable sized and encode type and
length information for each field and no table constraint changes this. The
table constraints only change how some values are interpreted.
On Thu, Aug 27, 2015 at 7:06 AM, Nicolas J?ger
wrote:
> Hi Darko, Igor and others.
>
On 8/26/2015 11:51 PM, Nicolas J?ger wrote:
> my error is obvious, but why sqlite doesn't return an error ?
http://sqlite.org/datatype3.html
--
Igor Tandetnik
Hi,
I have a table built by:
CREATE TABLE IF NOT EXISTS TAGS (ID INTEGER PRIMARY KEY AUTOINCREMENT,
NAME TEXT NOT NULL, COUNT INTEGER NOT NULL);
where `COUNT` is an `INTEGER`. I wanted to increment `COUNT` with that
command :
UPDATE TAGS SET COUNT = 'COUNT + 1' WHERE ID = '666';
but when I
Columns do not have a fixed type and will accept any type. It's not a bug,
it's a feature:
http://sqlite.org/datatype3.html
On Wed, Aug 26, 2015 at 8:51 PM, Nicolas J?ger
wrote:
> Hi,
> I have a table built by:
>
> CREATE TABLE IF NOT EXISTS TAGS (ID INTEGER PRIMARY KEY AUTOINCREMENT,
> NAME
11 matches
Mail list logo