Re: [sqlite] sqlite-users Digest, Vol 114, Issue 23

Thanks Chris! I'm using .Net 4.6 (VS 2017), which I don't think works with System.Data.SQLite yet, so I downgraded to .net 4.5.2. Seems to be working fine. Please tell me about your classes. I'm using EF6. -Original Message- From: sqlite-users

Re: [sqlite] UTF8-BOM not disregarded in CSV import

Hello, On 2017-06-23 22:12, Mahmoud Al-Qudsi wrote: I think you and I are on the same page here, Clemens? I abhor the BOM, but the question is whether or not SQLite will cater to the fact that the bigger names in the industry appear hell-bent on shoving it in users’ documents by default.

Re: [sqlite] operator precedence

On 25 Jun 2017, at 7:59pm, J Decker wrote: > SQL Standard > http://web.cecs.pdx.edu/~len/sql1999.pdf > doesn't seem to have math operators... and the precedence tables are > described in longhand without a simple table > DateTimes have math operators > > "Operations on

Re: [sqlite] operator precedence

Mysql has bitwise & before | https://dev.mysql.com/doc/refman/5.7/en/operator-precedence.html TSQL (MSSQL) has them equal. https://docs.microsoft.com/en-us/sql/t-sql/language-elements/operator-precedence-transact-sql Oracle doesn't have bitwise & and |

Re: [sqlite] operator precedence

On Sun, Jun 25, 2017 at 11:11 AM, x wrote: > > Is there a reason why sqlite doesn’t follow the c convention? > > e.g. & and | have equal precedence in sqlite. > I'd blame it on Postgresql operator precedence; but then it also doesn't seem to have bitwise & and | just

Re: [sqlite] operator precedence

x wrote: > Is there a reason why sqlite doesn’t follow the c convention? Yes. That reason is named "ISO/IEC 9075", but commonly called "the SQL standard". Regards, Clemens ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

[sqlite] operator precedence

Is there a reason why sqlite doesn’t follow the c convention? e.g. & and | have equal precedence in sqlite. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Providing incrementing column to query

Some suggestions, the validity of which depend on the context and whether some ordering must be preserved. Let T(C1 primary key,other_data) be the table with which we want to associate a sequence number (as pseudo column Seq). Technique 1: Computing Seq through a recursive CTE. create table

Re: [sqlite] JSON1 extension / json_patch / no such function

On 25 Jun 2017, at 10:36, David Empson wrote: > json_patch() was added to the json1 extension in SQLite 3.18.0, but the other > functions were there in earlier versions as far back as SQLite 3.9.0. Hi, I see... > Looking at https://sqlitestudio.pl/index.rvt?act=changelog it appears the >

Re: [sqlite] JSON1 extension / json_patch / no such function

json_patch() was added to the json1 extension in SQLite 3.18.0, but the other functions were there in earlier versions as far back as SQLite 3.9.0. Looking at https://sqlitestudio.pl/index.rvt?act=changelog it appears the latest version of SQLiteStudio (3.1.1) is using SQLite 3.15.0, so that is

[sqlite] JSON1 extension / json_patch / no such function

Hi, I'm trying to use the json_patch function in a query and tried in SQLiteStudio and my own program and both times I get a "Error: Database no such function: json_patch" The query I want to do is: UPDATE json_products SET json_value = json_patch(json_value,'{"col-1":1000}') json_extract