half Of Werner Kleiner
> Sent: Thursday, May 15, 2014 7:08 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] SQLite Datareader problems with Int?
>
> Simon Slavin-3 wrote
> > There is no need to do anything special. f you use 'Int' in SQLite
> > it will be
On 15 May 2014, at 12:53pm, Werner Kleiner wrote:
> What we use is this:
>
> System.Data.SQLite
> System.Data.SQLite Download Page
>
> http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
>
> And this is not part of SQLite?
Not really. As the page says
"System.Data.SQLite
What we use is this:
System.Data.SQLite
System.Data.SQLite Download Page
http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
And this is not part of SQLite?
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/SQLite-Datareader-problems-with-Int-tp75670p75
On 15 May 2014, at 12:08pm, Werner Kleiner wrote:
> Simon Slavin-3 wrote
>> There is no need to do anything special. f you use 'Int' in SQLite it
>> will be interpreted as 'INTEGER' anyway.
>
> Yes, but back to my datareader problem it seems that the Datareader differs
> between a column whi
Simon Slavin-3 wrote
> There is no need to do anything special. f you use 'Int' in SQLite it
> will be interpreted as 'INTEGER' anyway.
Yes, but back to my datareader problem it seems that the Datareader differs
between a column which is 'INTEGER' or 'Int'.
Especially we had a problem with a
On 15 May 2014, at 7:22am, Werner Kleiner wrote:
> What I mean is: The original MySQL DB has columns with int(10). And the
> converting tool converts all these columns in SQLite to Int
> I can change the conversion so that all columns would be INTEGER in SQLite.
> As I understand for SQLite it
On Thu, May 15, 2014 at 3:23 AM, Stephen Chrzanowski wrote:
> Technically, SQLite thinks STRING = INTEGER as far as field definitions are
> concerned, but either int or integer will do the job.
>
Not so. Please see http://www.sqlite.org/datatype3.html#affinity
SQLite version 2 stored all values
Integer and Int is equivalent in SQLite indeed, except in primary keys - where if you declare a primary key as INTEGER PRIMARY KEY
it becomes an alias for the rowid, and INT PRIMARY KEY is a normal Integer primary key but distinct from the rowid. In all other
cases they mean the same.
On 2014/
Technically, SQLite thinks STRING = INTEGER as far as field definitions are
concerned, but either int or integer will do the job.
On Thu, May 15, 2014 at 2:22 AM, Werner Kleiner wrote:
> What I mean is: The original MySQL DB has columns with int(10). And the
> converting tool converts all these
What I mean is: The original MySQL DB has columns with int(10). And the
converting tool converts all these columns in SQLite to Int
I can change the conversion so that all columns would be INTEGER in SQLite.
As I understand for SQLite it is equal if the column is declared as Int or
INTEGER?
--
On 14 May 2014, at 3:19pm, Kleiner Werner wrote:
> Could it be a problem or does it matter if we convert all SQLite int columns
> to INTEGER?
SQLite does not have an 'int(10)' type. For integers it has only INTEGER.
There should be no problem with the conversion.
There may be a problem late
Hello,
A program written in C# use SQLite datareader to read SQLite tables and columns.
We have some problems now with SQLite columns which are declared as "int" (not
INTEGER)
It seems that the SQlite datareader recognice these columns as integer 32 bit.
If we change the columns to "INTEGER" all
12 matches
Mail list logo
