Re: [sqlite] SQLite not performing a certain update

On 24/01/2009 5:09 AM, Onion Knight wrote: > "UPDATE tags SET lft = CASE WHEN lft BETWEEN ? AND ?" > " THEN lft + ? ELSE lft + ?" > "END WHERE lft BETWEEN ? AND ?", Two suggestions: (A) Check to see if the corresponding SELECT works: "SELECT *, CASE WHEN lft BETWEEN ?

Re: [sqlite] Effective way to use RTree to find the neighborhood ???

On 23/01/2009 12:58 AM, Igor Tandetnik wrote: > "Sergej Schwarz" wrote in > message news:20090122133954.74...@gmx.net >> unfortunately, this does not work, the RTree documentation by SQLite >> leads to misunderstanding of the concept... The query would results >> in an

Re: [sqlite] Date datatype

On 21/01/2009 10:09 PM, Paolo Pisati wrote: > It seems i'm having an hard time with dates in sqlite: > > sqlite> .schema > CREATE TABLE `envelope` (`smtp_id` int(10) NOT NULL, `date` date NOT > NULL, `time` time NOT NULL, `mailq_sndr` int(10) NOT NULL, > `delivery_sndr` int(10) NOT NULL,

Re: [sqlite] Recover deleted records

On 21/01/2009 7:03 AM, Alex Mandel wrote: > Griggs, Donald wrote: >> Hi Alex >> >> I can't answer your specific questions, but I presume you've already >> studied the file format document (most recently mentioned by Roger >> Binn's recent post): >> >> http://www.sqlite.org/fileformat.html >>

Re: [sqlite] [3.5.4] Fails importing CSV file

Gilles wrote: > At 22:47 04/02/2008 +1100, John Machin wrote: > >> Well, obviously(?) you are closer to success with "\t" than with '\t'. >> You probably have an extra unseen TAB. It won't like that NULL. >> > > Thanks, but no matter what I tr

Re: [sqlite] [3.5.4] Fails importing CSV file

Gilles wrote: > At 02:27 04/02/2008 +0100, Gilles wrote: > >> Thanks for the tip, but I tried that too, with no success: >> > > I tried both: > > sqlite> .separator "\t" > sqlite> .import test.csv customer > test.csv line 1: expected 3 columns of data but found 4 > > sqlite> .separator

Re: [sqlite] Re: Error in SQLite's CSV output

Dennis Cote wrote: John Machin wrote: U what about quoting the quote character? Line-ending characters e.g. \r and \n? sqlite> .mode csv sqlite> select 1, 'He said "Hello".', 3; 1,"He said "Hello".",3 should be 1,"He said ""Hello&

Re: [sqlite] Re: Error in SQLite's CSV output

Kees Nuyt wrote: On Wed, 19 Dec 2007 00:14:42 +1100, T <[EMAIL PROTECTED]> wrote: I think I've discovered yet another bug in the CSV output using the sqlite3 command line tool. Here's a sample of the new bug: .mode csv select 'a=1,234', 'b=5'; gives: a=1,234,b=5 but should give:

[sqlite] [OT] "encrypted" e-mail address (was Re: [sqlite] sqlite3Explorer)

Cariotoglou Mike wrote: you can't ?! I overdid it, then :) [snip] From: Joe Wilson [mailto:[EMAIL PROTECTED] Sent: Sat 11/24/2007 7:00 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3Explorer the address follows, obfuscated for the usual

Re: [sqlite] Sqlite insertion performance

On 17/09/2007 1:07 PM, Joe Wilson wrote: --- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote: I have been struggling with the performance of insertion in sqlite. Here we have a very simple case : A table with an integer autoincrement primary key and a text field that is unique. CREATE TABLE

Re: [sqlite] Re: select round(98926650.50001, 1) ?

On 5/09/2007 10:13 AM, John Stanton wrote: John Machin wrote: On 5/09/2007 6:18 AM, John Stanton wrote: These are regular floating point numbers, and behave accordingly. Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG. Precisely, As I said, regular floating po

Re: [sqlite] Re: select round(98926650.50001, 1) ?

On 5/09/2007 6:18 AM, John Stanton wrote: These are regular floating point numbers, and behave accordingly. Utter nonsense. round(98926650.5, 1) -> 98926650.501 is a BUG. 98926650.5 is representable EXACTLY in "regular" floating point. The round function should calculate a scale factor

Re: [sqlite] Re: select round(98926650.50001, 1) ?

On 4/09/2007 7:13 AM, Doug Currie wrote: On Monday, September 03, 2007 Nuno Lucas wrote: Maybe some OS specific error? Wasn't there some discussion earlier about the Microsoft compiler not using the full double precision by default? Microsoft C compilers store long doubles in 64 bits, just

Re: [sqlite] Difference between OR and IN [http://www.sqlite.org/php2004/page-052.html]

On 3/09/2007 1:00 AM, RaghavendraK 70574 wrote: Hi, create table test (column text); Please try pasting in SQL that actually runs. "column" is a reserved word. create index idx on text(column);[IN uses index] Please try pasting in SQL that actually runs. You need "test", not "text". Use

Re: [sqlite] BestMatch and SqliteStatment Clash

On 29/08/2007 10:37 PM, RaghavendraK 70574 wrote: Thx. I have modifed it to ?, but Sqlite fails to get records for the below query. When debug it retuns SQLITE_DONE. Pls help. select * from 'tbl.7' where ? like column1 || '%' order by column1 desc limit 1; Data is as below: Version: 3.4.0

Re: [sqlite] BestMatch and SqliteStatment Clash

On 29/08/2007 8:37 PM, RaghavendraK 70574 wrote: Hi, Am using sqlite 3.4.0 stmt= sqlite_prepareV2("select * from test where '?' like t || '%' order by t desc); ? is the sql variable. No it isn't; it's the contents of a string constant. Try this: select * from test where ? like t || '%'

Re: [sqlite] Increasing performance of joins with a group by clause?

On 19/08/2007 4:01 AM, Jef Driesen wrote: Suppose I have two related tables: CREATE TABLE events ( id INTEGER PRIMARY KEY NOT NULL, place_id INTEGER ); CREATE TABLE places ( id INTEGER PRIMARY KEY NOT NULL, name TEXT ); INSERT INTO places (id, name) VALUES (1, 'Place A');

Re: [sqlite] Re: SELECT INTO ... not supported?

On 18/08/2007 12:17 PM, Igor Tandetnik wrote: John Machin <[EMAIL PROTECTED]> wrote: Something as simple as SELECT * INTO tblcopy FROM tbl; (where tbl is an existing table) gets the following error: SQL error: near "INTO": syntax error [version: 3.4.2 on Win

[sqlite] SELECT INTO ... not supported?

Hi all, Something as simple as SELECT * INTO tblcopy FROM tbl; (where tbl is an existing table) gets the following error: SQL error: near "INTO": syntax error [version: 3.4.2 on Windows XP] I note that this syntax is not mentioned on the supported SQL syntax web page for SELECT, but

<    1   2   3