[sqlite] CAST STRING => INTEGER

On Tuesday, 15 March, 2016 07:46, James K Lowden wrote: > > 2. CAST(manydigitstext AS INTEGER) == {SMALLEST_INT64,LARGEST_INT64} > > --- your opinion as I understood you well; > Yes, if the string cannot be represented as an integer, CAST should > raise a range error. That spares the

[sqlite] ASK SQLite3 matchinfo() performance

Hi all. I've example database that can be downloaded here http://www.megafileupload.com/rhqU/product.db or you can generate yourself by using this python script:http://pastebin.com/4djPZJ21 I try to compare performance between standard query and using matchinfo() function.Standard

[sqlite] CAST STRING => INTEGER

On Tue, 15 Mar 2016 01:02:17 +0100 "Cezary H. Noweta" wrote: > 2nd row: why REALs can have trailing spaces, while INTEGERs cannot? > 3rd row: why REALs can have trailing trash, while INTEGERs cannot? I think we know now that string->integer conversion is pathologically broken for inputs that

[sqlite] SQLITE_USER_AUTHENTICATION

Hi, 1) When i use sqlite3_user_add it first checks whether sqlite_user table exists. 2) It tries to create sqlite_user table 3) It throws an error that sqlite_user is reserved for interal use. Regards, Siddharth On Tue, Mar 15, 2016 at 3:51 AM, syl leo wrote: > Hi, > I'm not a expert but i

[sqlite] SQLITE_USER_AUTHENTICATION

Hi, I had modified that for my convenience. I had changed it in the code also. I was under the impression to make it compatible for both 64 and 32 bit the underscore is required. I have tried it with and without the underscore. Both times it compiled successfully and all the operations worked

[sqlite] CAST STRING => INTEGER

Hello, On 2016-03-14 22:23, James K. Lowden wrote: > [...] Thank you for expanding my list of inconsistencies and things which can be done in an other manner, with good reasons why ``other'' could become ``better''. A rationale for my question was born while trying to fix rather obvious