[sqlite] XOR operator

Dear SQLite developers, I wanted to use the XOR operator in a query today, but then found out that SQLite doesn't support it. MySQL and Microsoft SQL both have XOR. Would you consider adding it to SQLite too? -Alex ___ sqlite-users mailing list

Re: [sqlite] Please remove multiple warnings from compiler about optimisation, variable conversion, signed overflow and many more potential errors.

Fixing the #if is only like 1-5% of the warnings he's complaining about... A large chunk of them are around comple options strings used for pragma compileoptions -- static const char * const azCompileOpt[] = { /* These macros are provided to "stringify" the value of the define ** for

Re: [sqlite] Please remove multiple warnings from compiler about optimisation, variable conversion, signed overflow and many more potential errors.

On 10/5/17 8:06 PM, James K. Lowden wrote: On Fri, 29 Sep 2017 16:55:05 -0400 Igor Korot wrote: But then why not give it some default value ("0" maybe") and default it to "1" only if needed during configure? Because complexity. It takes effort --- unnecessary effort --

Re: [sqlite] Please remove multiple warnings from compiler about optimisation, variable conversion, signed overflow and many more potential errors.

On Fri, 29 Sep 2017 16:55:05 -0400 Igor Korot wrote: > But then why not give it some default value ("0" maybe") and default > it to "1" only if needed during configure? Because complexity. It takes effort --- unnecessary effort -- to set up that default. That effort could

Re: [sqlite] Binding an order by

Interesting idea, and one for the books, but, in this case, the sort order is complicated by nothing being fixed. The primary sort concern is whether I'm grouping priorities of the tickets together or not. If grouped, the priority order is considered first [ order by Priority=0,Priority, ]. If

Re: [sqlite] Binding an order by

On 5 Oct 2017, at 7:59pm, Stephen Chrzanowski wrote: > No. The user (Me) can only select the order through popups, not by > entering a string. I understand the concern, but, depending on what the > user selects, the code will generate the string based on the users click.

Re: [sqlite] Binding an order by

What you may be able to do is to use a case statement(s) which uses a bound variable to either a column or dummy E.g order by case orderControlValue = 1 then column1 else "" end, ... On 10/5/2017 11:51 AM, Igor Tandetnik wrote: On 10/5/2017 2:45 PM, Stephen Chrzanowski wrote: Given the

Re: [sqlite] How to handle such situation

Hi Simon et al, So I shouldn't card if _close() fail either way? Just give an error and quit? Thank you. On Oct 5, 2017 2:01 PM, "Simon Slavin" wrote: On 5 Oct 2017, at 6:42pm, Igor Korot wrote: > My question here is about ROLLBACK failure vs

Re: [sqlite] Binding an order by

No. The user (Me) can only select the order through popups, not by entering a string. I understand the concern, but, depending on what the user selects, the code will generate the string based on the users click. On Thu, Oct 5, 2017 at 2:52 PM, Simon Slavin wrote: > > >

Re: [sqlite] Binding an order by

On 5 Oct 2017, at 7:45pm, Stephen Chrzanowski wrote: > I wanted to bind :OrderBy with field names and conditions based on user > preferences Binding is to values, not to column names. If you have one ORDER BY parameter, you can only bind it to a value. If you want a

Re: [sqlite] Binding an order by

That's all I needed to know. Thanks. On Thu, Oct 5, 2017 at 2:52 PM, Gwendal Roué wrote: > > > Le 5 oct. 2017 à 20:45, Stephen Chrzanowski a > écrit : > > > > Given the query: > > > > select EventID, Airline, ContactInfo,TicketID,CreateDate from

Re: [sqlite] Binding an order by

> Le 5 oct. 2017 à 20:45, Stephen Chrzanowski a écrit : > > Given the query: > > select EventID, Airline, ContactInfo,TicketID,CreateDate from tEvents where > Resolved=:Resolved order by :OrderBy > > I wanted to bind :OrderBy with field names and conditions based on user

Re: [sqlite] Binding an order by

On 10/5/2017 2:45 PM, Stephen Chrzanowski wrote: Given the query: select EventID, Airline, ContactInfo,TicketID,CreateDate from tEvents where Resolved=:Resolved order by :OrderBy I wanted to bind :OrderBy with field names You can't. A bound parameter can only appear where a literal is

[sqlite] Binding an order by

Given the query: select EventID, Airline, ContactInfo,TicketID,CreateDate from tEvents where Resolved=:Resolved order by :OrderBy I wanted to bind :OrderBy with field names and conditions based on user preferences, but I think the bind converted my order rules into a string and ordered my

Re: [sqlite] How to handle such situation

On 5 Oct 2017, at 6:42pm, Igor Korot wrote: > My question here is about ROLLBACK failure vs sqlite3_close() failure. > Like I said when the app closes I'm calling the latter and if it failed I > again display an error and just quit. > > But if the former fails calling

Re: [sqlite] How to handle such situation

Simon My question here is about ROLLBACK failure vs sqlite3_close() failure. Like I said when the app closes I'm calling the latter and if it failed I again display an error and just quit. But if the former fails calling _close() does not make much sense, right? Thank you. On Oct 5, 2017 11:50

Re: [sqlite] How to handle such situation

On 5 Oct 2017, at 4:35pm, Igor Korot wrote: > You mean like have some kind of flag and display an error on disconnect > only if not set? If ROLLBACK fails, it’s probably because of a hardware failure or your database being corrupt. You can’t do anything else useful with

Re: [sqlite] How to handle such situation

> On Oct 5, 2017, at 8:35 AM, Igor Korot wrote: > > You mean like have some kind of flag and display an error on disconnect only > if not set? That’s up to you; it depends on how your program is structured. If you treat it as a fatal error, you don’t need to worry about

Re: [sqlite] How to handle such situation

Jens, You mean like have some kind of flag and display an error on disconnect only if not set? Thank you. On Oct 5, 2017 11:32 AM, "Jens Alfke" wrote: > > > > On Oct 4, 2017, at 7:16 PM, Igor Korot wrote: > > > > And if the ROLLBACK fails? > > Then

Re: [sqlite] How to handle such situation

> On Oct 4, 2017, at 7:16 PM, Igor Korot wrote: > > And if the ROLLBACK fails? Then AFAIK, something’s really wrong; treat it as a fatal error, probably. —Jens ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org

Re: [sqlite] eponymous vtables, xBestIndex, and required parameters...

On 10/5/17, dave wrote: > > I suppose the converse is true, that the extimated cost > relative to OTHER virtual/physical tables does NOT matter. > It matters some, but it is of lesser importance. -- D. Richard Hipp d...@sqlite.org

Re: [sqlite] eponymous vtables, xBestIndex, and required parameters...

> ... > > 1) is there an orthodox method of indicating that a query > plan request from > > xBestIndex is a no-go, > > Give that plan a huge estimatedCost. > > As a backup, in the exceedingly unlikely event that SQLite chooses > your no-go plan in spite of the huge estimatedCost, also provide

[sqlite] SQLite extension library for calculating histograms

Hi, I want to announce an extension library I have created recently, SQLiteHistograms, that allows creating histogram tables, tables of average values of histogram bins as well as tables of ratios between histogram bins from existing SQLite database files. Available from:

Re: [sqlite] Sqlite3 Multi-process handling with continuous begin and commit in one thread cause error for other thread sqlite3_exec.

On 10/4/17, Hegde, Deepakakumar (D.) wrote: > > > 1) Open the Database in the two process > > 2) Both the link are added the busy handler and busy handler function is > retries for 1 times with 10ms second of delay. > > 3) In one thread there is a continuous record