SQLite Expert (which I use extensively in the Pro version) enforces
> displaying types as declared. So if you declare your column as INTEGER
> (or INT, ...) then it will display integers regardless of the actual
> individual data type using common conversions. This is a side effect
> of the Delph
Indeed, Igor, it is documented behavior, but my point was to reply to the
OP, who had written ruefully about SQLite's laissez-faire approach to
datatypes. For the OP's benefit, I wanted to demonstrate the behavior, show
what can be done with CAST, and then finally to show what can be done with
CAST
Tim Romano wrote:
> Ignore the typo:
>
> should be 2 | 2.2
>
>
> As someone who tends to make typogarphical errors, I do like forums with
> post-editing capabilities much better than mailing lists.
I don't. While this capability can be used benignly - fixing a typo or two -
too often I see it
Tim Romano wrote:
> So it would appear that if the numeric value to be inserted can be coerced
> to INTEGER without loss, it will in fact become an INTEGER, otherwise it
> stay what it was, REAL.
..., the behavior that is amply documented at http://sqlite.org/datatype3.html
--
Igor Tandetnik
__
Ignore the typo:
should be 2 | 2.2
As someone who tends to make typogarphical errors, I do like forums with
post-editing capabilities much better than mailing lists.
Regards
Tim Romano
Swarthmore PA
___
sqlite-users mailing list
sqlite-users@sqlite.or
I tried this in SQLite Manager for Firefox.
CREATE TABLE "PRODUCTS" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL
UNIQUE , "product" TEXT, "rank" INTEGER)
insert into products (product, rank) values ('gizmo', 1.0)
insert into products (product, rank) values ('widget', 2.0)
insert into produ
>
>
> SQLite Expert (which I use extensively in the Pro version) enforces
> displaying types as declared. So if you declare your column as INTEGER
> (or INT, ...) then it will display integers regardless of the actual
> individual data type using common conversions. This is a side effect
> of the
I understand, thanks a lot
Jean-Christophe Deschamps wrote:
> Ricardo,
>
>> I have typeof(basket)=real in all records ...
>> I just see now that all data are float numbers in the text file that was
>> used for inserting rows, and did not notice this because SqliteExpert
>> show only ints !
>
>
On 14 Jul 2010, at 2:19pm, Riccardo Cohen wrote:
> I have typeof(basket)=real in all records ...
> I just see now that all data are float numbers in the text file that was
> used for inserting rows, and did not notice this because SqliteExpert
> show only ints !
>
> I understand that sqlite a
Ricardo,
>I have typeof(basket)=real in all records ...
>I just see now that all data are float numbers in the text file that was
>used for inserting rows, and did not notice this because SqliteExpert
>show only ints !
SQLite Expert (which I use extensively in the Pro version) enforces
displayi
I have typeof(basket)=real in all records ...
I just see now that all data are float numbers in the text file that was
used for inserting rows, and did not notice this because SqliteExpert
show only ints !
I understand that sqlite accepts data that are not exactly in declared
format (other usu
Riccardo,
please do the following query
select typeof(basket) as tp FROM Data WHERE tp<>"integer"
as you may know sqlite accepts any value regardless of your desired type, so
you possible could have inserted a real value not knowing about it. This
query will probably show the rows with such valu
Hello
I've been using sqlite in many projects (thanks for providing it) and
found today someting strange with sum function
I have a simple database:
CREATE TABLE data (irisid char(9),postid varchar(20),basket integer);
CREATE INDEX irisididx on data (irisid);
CREATE INDEX postididx on data (post
13 matches
Mail list logo
