Re: [sqlite] Feature Request: Binding Arrays

Am 31.10.2013 14:09, schrieb Dominique Devienne: [Userdefined functions in conjunction with fast Exists-checks in "Userland" - vs. SQLites built-in indexing in case of In (List)] I'm not convinced by this. The "real table" can be quite large, several 100's to 100,000's rows (up to 1+ million

Re: [sqlite] Feature Request: Binding Arrays

On 01.11.2013 22:04, Alek Paunov wrote: After reading the whole tread I suspect that you have already considered the whole thing about the :memory: DB bridging the GUI with the real DB but I am curious why? Sorry - unfinished sentence: ... why you have rejected this approach?

Re: [sqlite] Feature Request: Binding Arrays

Hi Dominique, On 16.10.2013 11:40, Dominique Devienne wrote: We have an SQLite virtual-table heavy application with a lot of the GUI driven by SQL queries, and often times we have queries of the form ... create table t (name text, type text, primary key (name, type)); select * from t

Re: [sqlite] Feature Request: Binding Arrays

On 31.10.2013 18:37, Nico Williams wrote: On Wed, Oct 16, 2013 at 07:28:04AM -0400, Richard Hipp wrote: Please see http://www.sqlite.org/src/artifact/2ece66438?ln=13-75 I've been thinking for a while -ever since I happened upon jq(1)- that a marriage of jq and SQLite3 would be wonderful. jq

Re: [sqlite] Syntax of EXPLAIN QUERY PLAN "detail" column

On Fri, Nov 1, 2013 at 3:51 PM, Richard Hipp wrote: > I don't think anybody knows. The EXPLAIN QUERY PLAN syntax is not > formally > designed. It is intended for human reading, not machine parsing. It > changes from time to time and is not considered part of the SQLite >

Re: [sqlite] Syntax of EXPLAIN QUERY PLAN "detail" column

On Fri, Nov 1, 2013 at 9:38 AM, Constantine Yannakopoulos < alfasud...@gmail.com> wrote: > > Could > someone (probably an SQLite developer) tell me if this grammar covers all > cases of "detail" values or if there are cases I have missed? Maybe the > NGQP has introduced some changes I have

[sqlite] Syntax of EXPLAIN QUERY PLAN "detail" column

Hello all, I am trying to write a utility that processes the results of EXPLAIN QUERY PLAN statements and presents them in a graphical manner to developers. I need to extract information from the "detail" column of the returned result set (e.g. table name, index name, estimated rows etc.) and

Re: [sqlite] Dropping Trigger from Table

Thanks for all comments & suggestion. My Point : If we have trigger creation on per table basis then why can't we have dropping also on table basis. It is not good to have feature where each table owner are free to allow the way he want to create trigger. I can't quite decipher what you

Re: [sqlite] Inter Process Communincation using SQLite3 Trigger

Thanks for answer. I am in sync with your answer. I believe their is no risk from SQLite3 point of view to handle the mentioned case. On Fri, Nov 1, 2013 at 6:47 PM, Igor Tandetnik wrote: > On 11/1/2013 5:58 AM, techi eth wrote: > >> 1) Is process – B will allow to

Re: [sqlite] Dropping Trigger from Table

On 1 Nov 2013, at 1:15pm, techi eth wrote: > If we have trigger creation on per table basis then why can't we have > dropping also on table basis. TRIGGERs are not related to just one table. You can have a TRIGGER which mentions any number of tables. > It is not good to

Re: [sqlite] Dropping Trigger from Table

On Fri, Nov 1, 2013 at 2:15 PM, techi eth wrote: > It is not good to have feature where each table owner are free to allow the > way he want to create trigger. > sqlite does not offer per-table owners, nor any concept of "owners" at all, as is clearly stated in the docs:

Re: [sqlite] Storing sorted row order in a table

On 1 Nov 2013, at 4:54am, Igor Tandetnik wrote: > There is, but you probably won't like it. > > update myTable set currentOrder = 1 + > (select count(*) from myTable t2 where [t2 row comes before myTable row > according to order details]); You're right. I don't like

Re: [sqlite] Inter Process Communincation using SQLite3 Trigger

On 11/1/2013 5:58 AM, techi eth wrote: 1) Is process – B will allow to Insert? Sure, why not. 2) If allowed then it will select notify function from process – B or Process - A? The custom function will be called in process B - the process doing the insertion. 3) If all

Re: [sqlite] TRIGGER syntax

On 1 Nov 2013, at 4:59am, Igor Korot wrote: > I'm not sure I understand. > Are you saying that I don't have to populate the rank in the table on > insertion? Yes. >> Given your description above, why try to get all the ranks right every time >> you do an INSERT ? > >

Re: [sqlite] Dropping Trigger from Table

Thanks for all comments & suggestion. My Point : If we have trigger creation on per table basis then why can't we have dropping also on table basis. It is not good to have feature where each table owner are free to allow the way he want to create trigger. On Fri, Nov 1, 2013 at 6:33 PM,

Re: [sqlite] Dropping Trigger from Table

On 2013/11/01 14:41, techi eth wrote: I think so checking possible cases of any sqlite operation should not be called as bogus. Where ever I am not sure I will ask expert help & I have got all the time right answers. My point here is (and was) that the SQL you said that you have tried, is

Re: [sqlite] Dropping Trigger from Table

On Fri, Nov 1, 2013 at 1:41 PM, techi eth wrote: > Note: Trigger logic will be different but trigger names are same. > No, they won't, because you'll get an error when creating the second trigger with the same name. There is no per-table namespace for triggers. It is

Re: [sqlite] Dropping Trigger from Table

You seem to have a habit of inventing bogus SQL and then, when it doesn't work, ask for the correct form on here. If I was the forum police I would suggest reading some freely available on-line documents, but since I'm not. I think so checking possible cases of any sqlite operation should not be

Re: [sqlite] Dropping Trigger from Table

You seem to have a habit of inventing bogus SQL and then, when it doesn't work, ask for the correct form on here. If I was the forum police I would suggest reading some freely available on-line documents, but since I'm not - here's an attempt at answering the question: SQL is not a

Re: [sqlite] Dropping Trigger from Table

I don't understand what condition you might be talking about. As far as I know the functionality only allows you to simply drop a trigger, in your case: DROP TRIGGER trigger_name; or: DROP TRIGGER IF EXISTS trigger_name; Best regards, Daniel techi eth skrev 2013-11-01 12:53: How to

Re: [sqlite] Dropping Trigger from Table

On Fri, Nov 1, 2013 at 12:53 PM, techi eth wrote: > DROP TRIGGER trigger_name From tbl_name = TestTbl WHERE ; > Google "drop trigger sqlite" says: http://www.sqlite.org/lang_droptrigger.html -- - stephan beal http://wanderinghorse.net/home/stephan/

[sqlite] Dropping Trigger from Table

How to drop trigger from specific table with condition around? I tried this but got syntax error. DROP TRIGGER trigger_name From tbl_name = TestTbl WHERE ; Thanks ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Inter Process Communincation using SQLite3 Trigger

Hi, I understand SQLite3 will not be able to handle any IPC related operation. I am attempting my idea below to handle IPC with the help of SQLite3 Trigger. *Scenario:* I have two processes. Process – A will be responsible to create trigger & Process -B will doing operation like update,