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 5/13/2014 7:36 PM, Darren Duncan wrote:
Is something wrong with the configuration of this sqlite-users list?
A message of subject "Porting SQLite to plain C RTOS" was allowed and
distributed through it this morning with attachments.
Not only attachments, but about 5MB of attachments.
Quite
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
On 2014/05/14 09:56, Kleiner Werner wrote:
Hello,
A collegue has strange behavior with a sqlite database.
A "colleague" hey? This is not a "Dear John" column, you can be honest. :)
The original DB is about 13 MB.
After storing 40 entries in a table the disk space is double and about 26 M
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
On 14 May 2014, at 8:56am, Kleiner Werner wrote:
> A collegue has strange behavior with a sqlite database.
> The original DB is about 13 MB.
> After storing 40 entries in a table the disk space is double and about 26 MB.
I assume from fact that you're concerned about this that the data you're
i
On Wed, May 14, 2014 at 1:35 PM, Jan Slodicka wrote:
> Simon Slavin-3 wrote
> > On 13 May 2014, at 5:21pm, Constantine Yannakopoulos wrote:
> >
> >> This is very interesting Jan. The only way this could fail is if the
> >> collation implementation does something funny if it encounters this
> >>
Simon Slavin-3 wrote
> On 13 May 2014, at 5:21pm, Constantine Yannakopoulos wrote:
>
>> This is very interesting Jan. The only way this could fail is if the
>> collation implementation does something funny if it encounters this
>> character, e.g. choose to ignore it when comparing.
>
> That cut
Hick Gunter wrote:
> I was under the impression you wanted to achieve this:
>
> > select hex('abc' || X'10FFFD');
> 61626310FFFD
> > select length('abc' || X'10FFFD');
> 6
If you want to create characters through a blob, you have to use
the correct UTF-8 encoding:
sqlite> select quote(cast(char(
Dominique Devienne wrote
> On Tue, May 13, 2014 at 5:50 PM, Jan Slodicka <
> jano@
> > wrote:
>> So one could replace "LIKE 'xxx%'" by "BETWEEN('xxx', 'xxx' +
>> '\uDBFF\uDFFD').
>
> make that
>
> BETWEEN('xxx', 'xxx' + char(1114109))
>
> I don't think SQlite supports \u literals, nor does
Hello,
A collegue has strange behavior with a sqlite database.
The original DB is about 13 MB.
After storing 40 entries in a table the disk space is double and about 26 MB.
It is a program written in C# and used the SQLite datareader.
Now, suddenly he cannot get any returns from an simle select.
I was under the impression you wanted to achieve this:
asql> select hex('abc' || X'10FFFD');
hex('abc' || X'10FFFD')
---
61626310FFFD
asql> select length('abc' || X'10FFFD');
length('abc' || X'10FFFD')
--
6
asql> select typeof('abc' || X'10FFFD');
typeof
On Wed, May 14, 2014 at 8:30 AM, Hick Gunter wrote:
> Actually SQLite does support X'...' literals for creating blobs.
Note sure how that's relevant Hick. We don't need a blob, but a
integer for char(). I was obviously talking about *number* literals
(prefixed with 0b, 0, 0x for binary / octa
13 matches
Mail list logo
