It has to be something more complexof course, I tried the same database
in Debian Lenny + Sqlite3 3.5.9 and it works perfectly:
conxita@my_other_linux# sqlite3 backup_bd
SQLite version 3.5.9
Enter .help for instructions
sqlite .tables
android_metadata dbversion prefs
Any other ideas?
Hi,
You're wrong.
I think I've found the bug.
It is a parser issue.
According to their definition
(http://sqlite.org/syntaxdiagrams.html#single-source) , Join sources (named
single-source) are either :
* a table or view with an optional alias and/or with an optional index
* a
2012/3/22 Conxita Marín cma...@dims.com:
It has to be something more complexof course, I tried the same database in
Debian Lenny + Sqlite3 3.5.9 and it works perfectly:
conxita@my_other_linux# sqlite3 backup_bd
SQLite version 3.5.9
Enter .help for instructions
sqlite .tables
Shell .dump command produces incorrect output when using keyword as a
table name.
Example:
SQLite version 3.7.11 2012-03-20 11:35:50
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite CREATE TABLE table (column TEXT);
sqlite INSERT INTO table VALUES('value');
sqlite
Hi,
I have two tables like this:
CREATE TABLE IF NOT EXISTS folders (name TEXT NOT NULL ON CONFLICT
ROLLBACK, parent INTEGER REFERENCES folders (ROWID) ON DELETE CASCADE);
CREATE TABLE IF NOT EXISTS documents (document TEXT NOT NULL ON CONFLICT
ROLLBACK, folder_id INTEGER REFERENCES folders
On Thu, Mar 22, 2012 at 8:46 AM, Marko Mikkonen mmikk...@gmail.com wrote:
Hi,
I have two tables like this:
CREATE TABLE IF NOT EXISTS folders (name TEXT NOT NULL ON CONFLICT
ROLLBACK, parent INTEGER REFERENCES folders (ROWID) ON DELETE CASCADE);
CREATE TABLE IF NOT EXISTS documents
Thank you. I see now that it was in the documentation, but I just didn't
see it.
On 22.3.2012 14:48, Richard Hipp wrote:
PRAGMA foreign_keys=ON;
___
sqlite-users mailing list
sqlite-users@sqlite.org
There is a natural 5th extrapolation:
5) Could sqlite3 take advantage of multiple cpu's by parsing a single task
into one thread per cpu and segment data to be worked by each thread? Big
league stuff. But I don't think sqlite3 is meant to compete in that
market. It already exceeds expectations
Using sqlite3 python and I have a problem running a query.
My table has null values. Now if I do a 'select * from tablename' returns
to me as the result:
[(datetime.date (2012, 3, 22), buffer ptr read-write 0x03774B90,
0x03774B58 at size 0, None, None, None, None, None, None)]
As
Glubs!
Are yout right.
At some point I misspelled the name of the database by invoking sqlite
and even if you do nothing it writes an empty file.
Thank you and excuse me for that so silly question.
Conxita.
El 22/03/2012 10:27, Simon Davies escribió:
2012/3/22 Conxita
select * from tablename where field1 IS Null
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
boun...@sqlite.org] On Behalf Of Fabio Spadaro
Sent: Thursday, March 22, 2012 11:33 AM
To: General Discussion of SQLite Database
Subject: [sqlite] select null
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 = Null
select * from tablename where field1 is null;
NULL is never equal any value, not even another NULL.
--
Igor Tandetnik
___
On 22 Mar 2012, at 3:41pm, Igor Tandetnik itandet...@mvps.org wrote:
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 = Null
select * from tablename where field1 is null;
NULL is never equal any value, not even another NULL.
On 22 mars 2012, at 16:41, Igor Tandetnik wrote:
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 = Null
select * from tablename where field1 is null;
NULL is never equal any value, not even another NULL.
--
Igor Tandetnik
On 3/22/2012 12:18 PM, Jean-Denis MUYS wrote:
On 22 mars 2012, at 16:41, Igor Tandetnik wrote:
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 = Null
select * from tablename where field1 is null;
NULL is never equal any value,
I did show this very example, except lacking the whitespace in front
and differing in capitalization. I assume you feel those distinct
characteristics render your example more interesting than mine.
Or mine, which was sent minutes before Igor's. Hmph. ;)
On 22 mars 2012, at 17:26, Igor Tandetnik wrote:
On 3/22/2012 12:18 PM, Jean-Denis MUYS wrote:
On 22 mars 2012, at 16:41, Igor Tandetnik wrote:
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 = Null
select * from tablename
On 22 March, Jean-Denis wrote:
On 22 mars 2012, at 17:26, Igor Tandetnik wrote:
On 3/22/2012 12:18 PM, Jean-Denis MUYS wrote:
On 22 mars 2012, at 16:41, Igor Tandetnik wrote:
On 3/22/2012 11:32 AM, Fabio Spadaro wrote:
If I want to run a query like select * from tablename where field1 =
On Tue, Mar 20, 2012 at 8:25 PM, Jay A. Kreibich j...@kreibi.ch wrote:
On Tue, Mar 20, 2012 at 01:59:59PM -0700, Udi Karni scratched on the wall:
Is there a way to go directory from original to journal/final -
skipping the creation of the Temp version?
No, it requires all three copies.
...
For the time being - I have been avoiding the VACUUM of very large DBs by
creating a new iteration of the table/DB for each transformation instead of
using UPDATE/DELETE (given that I only have 1 table per DB) -
(1) create new DB_V2 / Table_V2
(2) attach DB_V1 / Table_V1
(3) insert into Table_V2
On Mar 22, 2012, at 11:19 PM, Udi Karni wrote:
Is there a way to run NOLOGGING in SQlite syntax - which means that if
something in the destination table/DB fails - you are prepared to just drop
it and start over?
PRAGMA journal_mode=off
http://sqlite.org/pragma.html#pragma_journal_mode
Very nice! Thanks !
But then - can you turn journaling off and then run a VACUUM and have it
run as a 2-step instead of a 3-step?
On Thu, Mar 22, 2012 at 3:25 PM, Petite Abeille petite.abei...@gmail.comwrote:
On Mar 22, 2012, at 11:19 PM, Udi Karni wrote:
Is there a way to run NOLOGGING
I'm planning to allow users to make database queries through a web
page. I'm thinking of letting the user provide the string that goes
between SELECT and FROM using the sqlite3 command tool, but what kind
of input checking is then needed?
Obviously, I need to check that the input doesn't contain
23 matches
Mail list logo
