Re: [sqlite] Re versing Text not Numbers

Macgyver7 wrote: > I tried the case function that was recommended, but that seems to recognise > everything in the column as text This means that everything in the column is in fact text. You do realize that '123' is not the same thing as 123, right? > except when

Re: [sqlite] Re versing Text not Numbers

Igor Tandetnik wrote: > > > That function can also check the type of its parameter and return it > unchanged if it's not a string. Or, you could do that in SQL: > > select (case when typeof(field) = 'text' then reverse(field) else field > end) > from myTable; > > I tried the case function

Re: [sqlite] Error: disk I/O error while creating an index

On 12/10/2011 06:01 AM, Tal Tabakman wrote: Hi, thanks for the reply. so, I don't have TMPDIR defined in my env. what is the behaviour of sqlite in such cases ? is there a default ? By default it will try /var/tmp, then /usr/tmp, then /tmp. SQLite creates temporary files there that it uses

Re: [sqlite] Error: disk I/O error while creating an index

On 10 Dec 2011, at 1:23am, Pavel Ivanov wrote: >> so, I can see the journal file in my work directory which I own (and >> in which the db file is placed). >> >> still constantly, I have a disk I/O ERROR which I don't understand. > > If you see journal file along your database file and each

Re: [sqlite] Error: disk I/O error while creating an index

> so, I can see the journal file in my work directory which I own (and > in which the db file is placed). > > still constantly, I have a disk I/O ERROR which I don't understand. If you see journal file along your database file and each attempt to open database doesn't delete journal file it means

Re: [sqlite] Error: disk I/O error while creating an index

Hi, thanks a lot. so, I can see the journal file in my work directory which I own (and in which the db file is placed). still constantly, I have a disk I/O ERROR which I don't understand. the db is only 64M on disk and I have plenty of space. how can I get to the bottom of this ? can it be

Re: [sqlite] Error: disk I/O error while creating an index

On 9 Dec 2011, at 11:01pm, Tal Tabakman wrote: > so, I don't have TMPDIR defined in my env. what is the behaviour of > sqlite in such cases ? is there a default ? The journal file will be created in the same directory as the database file. For this to work, your application and user must have

[sqlite] Error: disk I/O error while creating an index

Hi, thanks for the reply. so, I don't have TMPDIR defined in my env. what is the behaviour of sqlite in such cases ? is there a default ? cheers Tal On 12/09/2011 04:02 PM, Tal Tabakman wrote: >* Hi Guys,*>* I have an SQLITE database of 1.5 million rows in a single >table*>* each raw looks

Re: [sqlite] Unable to retrieve columns with table accessor on nested joins.

> -Ursprüngliche Nachricht- > Von: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] Im Auftrag von Jay A. Kreibich > Gesendet: Freitag, 9. Dezember 2011 17:42 > An: General Discussion of SQLite Database > Betreff: Re: [sqlite] Unable to retrieve columns with

Re: [sqlite] Unable to retrieve columns with table accessor on nested joins.

On Fri, Dec 09, 2011 at 01:12:26PM +, Fabrizio Steiner scratched on the wall: > Hello > > I'm currently facing a problem with nested right hand joins. I've also > reported this to the mailing list over one month ago, but haven't > received any reply. In the meantime I've investigated the

Re: [sqlite] Unable to retrieve columns with table accessor on nested joins.

Seems like the patch didn't get through, let's try again. Regards Fabrizio -Ursprüngliche Nachricht- Von: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] Im Auftrag von Fabrizio Steiner Gesendet: Freitag, 9. Dezember 2011 14:12 An: 'sqlite-users@sqlite.org'

[sqlite] Unable to retrieve columns with table accessor on nested joins.

Hello I'm currently facing a problem with nested right hand joins. I've also reported this to the mailing list over one month ago, but haven't received any reply. In the meantime I've investigated the problem in the SQLite source and sorted some things out. Let's first start with an example

Re: [sqlite] FTS Tokenizer (separator)

On Fri, Dec 9, 2011 at 6:48 AM, Ephraim Stevens wrote: > Greetings All, > > From section seven of the FTS3/FTS4 documentation: > > A term is a contiguous sequence of eligible characters, where eligible > characters are all alphanumeric characters, the "_" character, and

[sqlite] FTS Tokenizer (separator)

Greetings All, >From section seven of the FTS3/FTS4 documentation: A term is a contiguous sequence of eligible characters, where eligible characters are all alphanumeric characters, the "_" character, and all characters with UTF codepoints greater than or equal to 128. All other characters are

Re: [sqlite] Error: disk I/O error while creating an index

On 9 Dec 2011, at 9:02am, Tal Tabakman wrote: > CREATE INDEX IND1 ON ENTRIES (snum) > > the result I get is: > > Error: disk I/O error > > can you advice how to debug this one ? Before your 'CREATE INDEX' command try typeing .stats ON It may or may not do something, depending on which

Re: [sqlite] Error: disk I/O error while creating an index

On 12/09/2011 04:02 PM, Tal Tabakman wrote: Hi Guys, I have an SQLITE database of 1.5 million rows in a single table each raw looks like: 149|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1| now, from the sqlite command line interface I am creating an on a sincle integer column CREATE

[sqlite] Error: disk I/O error while creating an index

Hi Guys, I have an SQLITE database of 1.5 million rows in a single table each raw looks like: 149|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1| now, from the sqlite command line interface I am creating an on a sincle integer column CREATE INDEX IND1 ON ENTRIES (snum) the result I get