Re: [sqlite] Return failure from User Defined Function

RAKESH HEMRAJANI wrote: > How to return failure from a user defined function such that it halts the > main query? sqlite3_result_error* -- Igor Tandetnik ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Return failure from User Defined Function

Hello Experts, How to return failure from a user defined function such that it halts the main query? for example: assuming i have simple user defined function checkLessThanTen(arg 1) While calling this function in my query (say select checkIsNumber('11') from employee) how to

Re: [sqlite] connect to sqlite using OLE-DB or ODBC

Hi Oliver, Thanks for the reply. I will try it. Andi On 28/03/2011 10:37 PM, Oliver Peters wrote: > Andi Suhandi writes: > >> Hi guys, >> >> I am a newbie in sqlite. Is it possible to connect sqlite db using >> OLE-DB or ODBC ? >> If possible, what do i need ? >> > for ODBC

Re: [sqlite] connect to sqlite using OLE-DB or ODBC

Hi Simon, I use C++ language for my program Andi On 28/03/2011 7:02 PM, Simon Slavin wrote: > On 28 Mar 2011, at 12:14pm, Andi Suhandi wrote: > >> I am a newbie in sqlite. Is it possible to connect sqlite db using >> OLE-DB or ODBC ? >> If possible, what do i need ? > What programming language

[sqlite] signal 6 received due to assert_fail when writing DB

The version is 3.7.5 The GDB core dump is shown as below. gdb) bt #0 0x36a86b04 in raise () from /lib/libc.so.6 #1 0x36a882f4 in abort () from /lib/libc.so.6 #2 0x36a7e2a4 in __assert_fail () from /lib/libc.so.6 #3 0x100dc958 in btreeInvokeBusyHandler () #4 0x1013f1f4 in sqlite3VdbeHalt () #5

Re: [sqlite] Update trigger

On Tue, Mar 29, 2011 at 11:32 AM, Simon Slavin wrote: > On 29 Mar 2011, at 4:12pm, Sutter, Doug wrote: >> I know how to create a unique trigger for each column where I hard-code >> the column's name as shown below.  But I would like to create a trigger >> that would fire

Re: [sqlite] Update trigger

On 29 Mar 2011, at 4:12pm, Sutter, Doug wrote: > I know how to create a unique trigger for each column where I hard-code > the column's name as shown below. But I would like to create a trigger > that would fire when any column is updated and log the specific details > for that column only.

Re: [sqlite] Extremely large values error

On 29.03.2011 15:17, Max Vlasov wrote: > Thanks, this forced me to search more on the topic. I use Delphi and it > appears that all Borland compilers has their own floating-point exception > handling chain and it is on by default so if any division by zero or > overflow appears inside

[sqlite] Update trigger

Hi, I am trying to create a trigger that will log changes made to my database. I need to log only the columns that were updated (not the entire record). So I need to be able to log the column name, old value, new value and date/time. I also need to know which row was updated (identified by

Re: [sqlite] unexpected deadlocks in shared cache mode with unlock_notify

Hi, Boris Kolpackov writes: > Half of the threads executes the following transaction: > > BEGIN > INSERT > INSERT > INSERT > COMMIT > > The other half of the threads runs the following transaction: > > BEGIN > SELECT > UPDATE > COMMIT > > As expected, I periodically get

Re: [sqlite] Generate a unique id unless it is provided

I don't understand how your column C works...so I'll assume it's pre-known for now. But here's how to get A/B to work. drop table t if exists; create table t(a int,b int,c int); create trigger trig1 after insert on t begin update t set a=(select count(b) from t where b=new.b) where a=0; end;

Re: [sqlite] Extremely large values error

On Tue, Mar 29, 2011 at 3:56 PM, Richard Hipp wrote: > On Tue, Mar 29, 2011 at 4:48 AM, Max Vlasov wrote: > > > Hi, > > > > I sometimes use repeated digits as test data, for example 123456789 > > repeated > > multiply times and recently some of my complex

Re: [sqlite] bug with sqlite

Just to help clarify (hopefully) the Unix/Windows "reserved filename". CON: is similar to Unix's /dev/zero or /dev/null for example -- Files that already exist and have OS meaning. stdout is NOT a reserved filename...it's a predefined variable of FILE *. You cannot say "cp file stdout" on

Re: [sqlite] Generate a unique id unless it is provided

Tobias Vesterlund wrote: > I got a table in my database which looks like the following: > > A | B | C > 1 | 119 | 0 > 1 | 120 | 1 > 1 | 121 | 0 > 2 | 120 | 2 > 2 | 121 | 2 > > I want the A value to be generated

Re: [sqlite] Extremely large values error

On Tue, Mar 29, 2011 at 4:48 AM, Max Vlasov wrote: > Hi, > > I sometimes use repeated digits as test data, for example 123456789 > repeated > multiply times and recently some of my complex queries where I occasionally > wrongly chose a field gave 'unknown error' in the

Re: [sqlite] bug with sqlite

On 29 Mar 2011, at 12:38pm, Arjen Markus wrote: > is this under Windows? con is one of the reserved file names, dating > from the DOS days (or even before that). Bah. Arjen beat me to it. Yes 'con' is the filename you used to use when you wanted to talk to the CONSOLE: the terminal connected

[sqlite] Generate a unique id unless it is provided

Hi, I got a table in my database which looks like the following: A | B | C 1 | 119 | 0 1 | 120 | 1 1 | 121 | 0 2 | 120 | 2 2 | 121 | 2 I want the A value to be generated for the bold rows (ie first inserts of each 'linked' item) and I'd like to

Re: [sqlite] bug with sqlite

Windows doesn't allow "con" named fodlers or files. Marian Cascaval From: Felix Zimmermann To: sqlite-users@sqlite.org Sent: Mon, March 28, 2011 10:26:59 PM Subject: [sqlite] bug with sqlite hi why isnt it possible to create a database

Re: [sqlite] bug with sqlite

Hi, is this under Windows? con is one of the reserved file names, dating from the DOS days (or even before that). Other reserved names are aux, nul and prn (I think there is a fifth, but I cannot remember that one). So, that has nothing to do with SQLite itself. Regards, Arjen On 2011-03-28

[sqlite] bug with sqlite

hi why isnt it possible to create a database file with the name "con" ? i just doesnt work. no matter what file extension im taking. regrets Felix ___ sqlite-users mailing list sqlite-users@sqlite.org

Re: [sqlite] Extremely large values error

On Tue, Mar 29, 2011 at 4:05 AM, Cory Nelson wrote: > On Tue, Mar 29, 2011 at 1:48 AM, Max Vlasov wrote: >> Hi, >> >> I sometimes use repeated digits as test data, for example 123456789 repeated >> multiply times and recently some of my complex queries

Re: [sqlite] Extremely large values error

On Tue, Mar 29, 2011 at 1:48 AM, Max Vlasov wrote: > Hi, > > I sometimes use repeated digits as test data, for example 123456789 repeated > multiply times and recently some of my complex queries where I occasionally > wrongly chose a field gave 'unknown error' in the middle

Re: [sqlite] unexpected deadlocks in shared cache mode with unlock_notify

Hi Simon, Simon Slavin writes: > On 29 Mar 2011, at 10:48am, Boris Kolpackov wrote: > > > If I add IMMEDIATE (or EXCLUSIVE) to the first transaction > > (three INSERTs), nothing changes, [snip] > > > > If I add IMMEDIATE to the second transaction (SELECT then UPDATE), then > > the deadlocks go

Re: [sqlite] unexpected deadlocks in shared cache mode with unlock_notify

On 29 Mar 2011, at 10:48am, Boris Kolpackov wrote: > If I add IMMEDIATE (or EXCLUSIVE) to the first transaction > (three INSERTs), nothing changes, [snip] > > If I add IMMEDIATE to the second transaction (SELECT then UPDATE), then > the deadlocks go away for both transaction as one would

Re: [sqlite] unexpected deadlocks in shared cache mode with unlock_notify

Hi Simon, Simon Slavin writes: > On 28 Mar 2011, at 8:45pm, Boris Kolpackov wrote: > > > As expected, I periodically get deadlocks (SQLITE_LOCKED return code from > > unlock_notify()) for the second transaction due to the read to write > > lock upgrade. But I also get deadlocks reported for the

[sqlite] Extremely large values error

Hi, I sometimes use repeated digits as test data, for example 123456789 repeated multiply times and recently some of my complex queries where I occasionally wrongly chose a field gave 'unknown error' in the middle of the process. Tracking it led to sqlite3AtoF function that appears to be raising