[sqlite] To use or not to use single quotes with integers

Hi, I'm a beginner with sqliteand used to insert values in the fields of datatype text with single quote and values of datatype integer without single quote. But I realized that sqlite accepts inserting both data types (text and integer) with single quote without error. For example the

Re: [sqlite] To use or not to use single quotes with integers

On 8 Apr 2018, at 11:54am, Markos wrote: > CREATE TABLE foods( > id integer PRIMARY KEY, > type_id integer, > name text ); > > I can insert type_id without single quote: > > INSERT INTO foods (name, type_id) VALUES ('Rice', 16); > > And also with single quote: > >

[sqlite] UPPER function depends on Locale?

Hi, I am new in this list and this is my first post. The UPPER function is not working properly in Turkish language?! How can I get this? For example small "i" is equal to big "I" in Turkish language. But it's not working properly?! Thanks in advance... -- Regards, Mucip:)

Re: [sqlite] UPPER function depends on Locale?

On 8 Apr 2018, at 12:50pm, Dr. Mucibirahman İLBUĞA wrote: > The UPPER function is not working properly in Turkish language?! How can I > get this? > > For example small "i" is equal to big "I" in Turkish language. But it's not > working properly?! Can you paste into

Re: [sqlite] UPPER function depends on Locale?

On 8 Apr 2018, at 9:55pm, Dr. Mucibirahman İLBUĞA wrote: > As you see above table it returns incorrect. Only i>>I is working like in > English language?! When I use this code in PostgreSQL it works correct. But I > got unexpected result in SQLite unfortunatelly. Thank

Re: [sqlite] UPPER function depends on Locale?

08.04.2018 23:23 tarihinde Simon Slavin yazdı: Can you paste into a reply to this message some lower-case Turkish text, what you expect to get, and what you are getting instead ? It would be useful to have an example of what is going wrong. Dear Simon, First of all thanks a lot for your

Re: [sqlite] UPPER function depends on Locale?

Dear Simon, I develop project on QT/C++ and compile both Linux and Windows platforms. In this case, should I recompile SQLite both of these platforms?! Should I make some modifications on QT too?! By the way is there any good guidence to add ICU support to SQLite both Linux and Windows

Re: [sqlite] UPPER function depends on Locale?

Dear Simon, OK. Thanks. It seems that I need to make moore Google search about "Recompiling SQLite with ICU"... Regards, Mucip:) On Mon, Apr 9, 2018 at 12:56 AM, Simon Slavin wrote: > On 8 Apr 2018, at 10:51pm, mucip.ilb...@gmail.com wrote: > > > I develop project on

Re: [sqlite] UPPER function depends on Locale?

On 8 Apr 2018, at 10:51pm, mucip.ilb...@gmail.com wrote: > I develop project on QT/C++ and compile both Linux and Windows platforms. > In this case, should I recompile SQLite both of these platforms?! Should I > make some modifications on QT too?! I think you will need to do all these things. I

[sqlite] Documentation update

"For the purposes of unique indices, all NULL values are considered [to] different from all other NULL values and are thus unique." I think it should read "...NULL value are considered different..." https://www.sqlite.org/lang_createindex.html dvn ___

Re: [sqlite] Documentation update

On 9 Apr 2018, at 1:08am, Don V Nielsen wrote: > "For the purposes of unique indices, all NULL values are considered [to] > different from all other NULL values and are thus unique." > > I think it should read "...NULL value are considered different..." > >

Re: [sqlite] Missing keywords

Klaas Van B. wrote: > Since 3.23 the words FALSE and TRUE should be added to SQLite Query Language: > SQLite Keywords. But FALSE and TRUE are not keywords. says that | keywords ... may not be used as the names of tables, indices, columns, | ... or any

[sqlite] Constraining FTS5 results based on offsets()

Hi, For my use case I need to index some texts, and I also need be able to assign attributes to sub-sequences/spans of tokens in the texts. I want to be able to search only for keywords/phrases that occur in spans with a certain attribute. As an example, imagine we have a set of rich text

Re: [sqlite] Documentation update

"to be", or not "to be" :) On Sun, Apr 8, 2018 at 7:08 PM, Don V Nielsen wrote: > "For the purposes of unique indices, all NULL values are considered [to] > different from all other NULL values and are thus unique." > > I think it should read "...NULL value are