Re: [sqlite] oracle compatibility mode

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 07:17 PM, Phil Oertel wrote: > Sorry for being unclear, I'm referring to the ability to emulate > oracle-specific features and syntax, like ROWNUM for example. What else? ROWNUM seems spectacularly useless! You should be able to use

Re: [sqlite] VFS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 02:39 PM, Robert Hairgrove wrote: > On Tue, 2011-02-22 at 08:46 -0800, Roger Binns wrote: >> What you think you are seeing is not happening. The documentation is >> correct. > > OK ... but what about that w

Re: [sqlite] VFS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2011 05:29 AM, Robert Hairgrove wrote: > I'm trying to understand how the VFS implementation works. What you think you are seeing is not happening. The documentation is correct. > However, if I open a database and inspect the VFS

Re: [sqlite] Scrolling through results of select

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> 1. Is there any significant overhead on SQLite from my selecting from a >>> view representing the original arbitrary select? That is, will SQLite still >>> use any indexes etc correctly? Or do I need to dissect/parse the original >>> select

Re: [sqlite] SQLite server using execnet ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/21/2011 12:37 PM, Jay A. Kreibich wrote: > Yes, but in something like memcached, the database is not aware of > that structure, and can't take advantage of it. Memcached does understand some types and has atomic increment/decrement etc but

Re: [sqlite] SQLite server using execnet ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2011 06:23 PM, Jay A. Kreibich wrote: > On Sun, Feb 20, 2011 at 05:23:09PM -0800, Roger Binns scratched on the wall: >> If you want to use SQL then use Postfix. > > I might suggest PostgreSQL instead. > (Sorry, Roger,

Re: [sqlite] Upgrade from 3.5.8 -> 3.7.5 - increase memory usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2011 02:48 PM, Todd Shutts wrote: > However; memory usage is growing like crazy. It is a very frequent occurrence that what people think is being measured is not what is actually being measured. Make sure you understand exactly what the

Re: [sqlite] Fwd: Scrolling through results of select

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2011 04:47 PM, BareFeetWare wrote: > How can I best scroll though the results of an arbitrary select query? If you have infinite time and memory then there is no problem. You haven't stated your constraints or how arbitrary "arbitrary"

Re: [sqlite] SQLite server using execnet ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2011 04:55 PM, Stef Mientki wrote: > still want to see if a simple client/server setup would solve my current > problems There is no such thing as "simple" client/server. You have to worry about issues like authentication and

Re: [sqlite] Implementing custom xRead() and xWrite() routines for sqlite3_vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/20/2011 02:32 AM, Robert Hairgrove wrote: > There are certain parts of an SQLite database or page header (the first > 100 bytes, for example) which have known values. I think it is perhaps > even dangerous to encrypt this data, at least with the

Re: [sqlite] Implementing custom xRead() and xWrite() routines for sqlite3_vfs

On 02/20/2011 01:10 AM, Robert Hairgrove wrote: > I saw that, but I find it a little intrusive, programmatically speaking, > from a licensing standpoint. Why don't you ask DRH then since you won't be the first to want to include SEE with QT and a commercial app? > I am not starting from scratch

Re: [sqlite] Is it possible to determine how many openconnections are active for a sqlite database?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/19/2011 09:25 PM, Frank Chang wrote: > >I wanted to thank Roger Binns for solving my problem. You are welcome :-) > I was able to determine the sqlite database was corrupted Just to be clear for people finding this thread in t

Re: [sqlite] Implementing custom xRead() and xWrite() routines for sqlite3_vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/19/2011 04:04 PM, Simon Slavin wrote: > An alternative to the 'straight SQLite' solution would be to write your own > routine to dump to disk instead of using the backup API. I have no idea > whether this would be better or worse, It would

Re: [sqlite] Implementing custom xRead() and xWrite() routines for sqlite3_vfs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/19/2011 03:40 PM, Robert Hairgrove wrote: > But before I "try this at home", I thought I would ask if there are any > caveats I should be aware of? Thanks for any helpful advice! Unless your time has no value, I'd suggest using this:

Re: [sqlite] iIs it possible to determine how many open connections are active for a sqlite database?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 07:24 PM, Frank Chang wrote: > As a result, I periodically get a sqlite return code of 1 from sqlite3_step > after inserting one of the 5.4 million rows. That just means there was an error. You still need to sqlite3_reset to find out

Re: [sqlite] SQLite and SIGFPE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 07:03 PM, Nico Williams wrote: > BUT, because SIGFPE is a synchronous > signal so you are on much firmer ground: you can't block it, Incidentally you can block it sometimes but the mechanism is very operating system specific. For

Re: [sqlite] EXT :Re: Compiler warnings in R-Tree code under Visual StudioExpress

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 06:32 AM, Black, Michael (IS) wrote: > You can actually have both you know, working and no warnings...I do it all > the time. And what evidence do you have it actually works? This is what the SQLite team has:

Re: [sqlite] SQLite version 3.7.6 testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2011 02:13 PM, Richard Hipp wrote: >> But SQLITE_ENABLE_STAT2 breaks that guarantee. With STAT2, the ANALYZE >> command stores a histogram of left-most column of each index in order to >> help it make decisions about whether or not to use

Re: [sqlite] UPDATE/INSERTing 1-2k rows slower than expected

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2011 11:54 AM, Simon Slavin wrote: > Compensating for this behaviour is a big part of what SQLite does in > journaling. SQLite and other journalling mechanisms depend on an operating system call fsync that flushes their relevant data to

Re: [sqlite] SQLite version 3.7.6 testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2011 11:40 AM, Simon Slavin wrote: > Does it make the ANALYZE command take significantly longer ? I don't think that matters. If someone runs ANALYZE it is because they are experiencing performance issues using default (non-analyzed) query

Re: [sqlite] SQLite version 3.7.6 testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/2011 07:27 AM, Richard Hipp wrote: > ... if SQLite is compiled using SQLITE_ENABLE_STAT2 ... Is there any reason this is not turned on by default? If it is turned on and then the database is used by an earlier version of SQLite will there

Re: [sqlite] completion of sql words

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/11/2011 02:30 PM, Simon Slavin wrote: > Although you can download a command-line tool for sqlite3 from the sqlite3 > web site, it's provided just for convenience and many people don't use it (or > even know about it). On Unix platforms that

Re: [sqlite] sqlite async

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/08/2011 09:50 PM, Mike Blumenkrantz wrote: > I have checked out the documentation and found information about > using sqlite in async mode with threads, Do you mean this? http://www.sqlite.org/asyncvfs.html > but I am wondering if there is

Re: [sqlite] Feature Request: PRAGMA foreign_key_list(tableName) should display the name of the foreign key constraint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/08/2011 07:55 PM, BareFeetWare wrote: > Currently, I have to run pragma foreign_key_list() for each of my tables, ... Create virtual table(s) and query those as needed. Use the experience to document what worked best, any gotchas and as

Re: [sqlite] Question about database design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2011 11:48 AM, Bert Nelsen wrote: > Because I felt so stupid about these mostly empty columns taking so much > space, I tended to replace all the "phone" columns by a single column named > "customerPhone". > I stored the values into

Re: [sqlite] SQLite version 3.7.5 - code freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > A far better solution ... would be to bump > the VFS version number to 3 That is the only solution that will not break any existing code from anyone. ie you have to use VFS 3 to opt in to getting SYNC_OMITTED (probably best delivered to

Re: [sqlite] SQLite version 3.7.5 - code freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/25/2011 08:56 AM, Richard Hipp wrote: >> Thanks for the helpful feedback. Please let us know if you find this >> solution inadequate or if you encounter other problems. A far better solution to this kind of thing is to do them the other way

Re: [sqlite] SQLite version 3.7.5 - code freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/24/2011 09:27 PM, Dan Kennedy wrote: > Does the aspw xFileControl method modify the value of the output > parameter in this case? No. > The idea was that existing VFS implementations would return SQLITE_ERROR > since they do not recognize

Re: [sqlite] SQLite version 3.7.5 - code freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/24/2011 06:05 PM, Roger Binns wrote: > I'm finding custom VFS code is no longer working at all. The cause is a new xFileControl operation SQLITE_FCNTL_SYNC which appears to needlessly duplicate the existing xSync method. Additionally unl

Re: [sqlite] SQLite version 3.7.5 - code freeze

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/24/2011 10:12 AM, Richard Hipp wrote: > Unless serious problems I'm finding custom VFS code is no longer working at all. Mine "inherits" from an existing one overriding or calling the original methods as appropriate. My code for this is

Re: [sqlite] Select statement not returning any result

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/16/2011 08:30 AM, Navaneeth.K.N wrote: > However, I am wondring why the function (sqlite3_bind_text) don't > respect NULL character in the string and stop reading when it find > one? Others have pointed out the API allows for you to ask exactly

Re: [sqlite] R: R: Crypto lib for Sqlite - suggest required

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2011 06:41 AM, Adam DeVita wrote: > The HASP envelope does prevent an executable from running with a > debugger open. Only in simple cases. Since the executable and the key are in the hands (and total control) of the adversary, they can do

Re: [sqlite] R: R: Crypto lib for Sqlite - suggest required

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/09/2011 02:20 AM, Marco Turco wrote: > My app is an accounting system. > This accounting system must support the exchange of db between users that > work with the this application > so I think the only way is to use the same key for all users.

Re: [sqlite] Corrupted database file.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/05/2011 11:05 AM, Greg Morehead wrote: > Any insights on how this could occur would be greatly appreciated. http://www.sqlite.org/lockingv3.html#how_to_corrupt Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment:

Re: [sqlite] R: Crypto lib for Sqlite - suggest required

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2011 04:36 AM, Marco Turco wrote: > Essentially I would avoid that my competitors can look inside the Db > structure and import data. On any machine where the database is used the key will have to exist in plain form no matter how convoluted

Re: [sqlite] Rollback transaction if error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/27/2010 06:37 PM, BareFeetWare wrote: > Yes, I know that in my application code I can step through each command in > the transaction, check for an error, and if there is an error, end the > transaction with a "rollback" instead of a "commit".

Re: [sqlite] last_insert_rowid() question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/27/2010 11:41 AM, Scott A Mintz wrote: > I know that I can use sqlite3_last_insert_rowid() to retrieve the value. > However, in a multi-threaded environment, it's possible for another thread > to do an INSERT before I get the first result.

Re: [sqlite] sqlite3 backup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/17/2010 03:30 AM, Fabio Spadaro wrote: > I use Python's sqlite3. > it is possible to backup a database without > use the copy command file? The pysqlite/sqlite3 module does not provide the backup API functionality, nor is its "dumper" that

Re: [sqlite] Virtual table optimization using xBestIndex/xFilter

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/2010 04:21 AM, Sören Brunk wrote: > I'm wondering if there is any way to pass that additional information to > xFilter besides encoding it into idxNum/idxStr somehow. That is the mechanism to use. Remember that internally SQLite uses only

Re: [sqlite] What is sqlite3_stmt_readonly for?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/08/2010 11:39 PM, Andy Gibbs wrote: > It looks like our calls did not go unheeded: it seems now to be fixed here > http://www.sqlite.org/src/info/9c19b7ae35. The question of why the existing authorizer functionality is insufficient or has some

Re: [sqlite] What is sqlite3_stmt_readonly for?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/07/2010 11:57 PM, Andy Gibbs wrote: > But what I wonder is, for what purpose it can be used? On the face of it, > it seems very useful, but then as you read through the description you find > a whole load of statement types that return an

Re: [sqlite] SQLite-3.7.4 Amalgamation?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/07/2010 08:45 PM, Darren Duncan wrote: > I am also working with automated scripts, which now have to be updated to use > either the new style or old style depending on the user-requested SQLite > version. (DBD::SQLite bundles a SQLite

Re: [sqlite] virtual tables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/23/2010 02:04 AM, Vivien Malerba wrote: > The Libgda library (http://www.gnome-db.org) uses virtual tables Are you sure? It looks like an abstraction layer that sits above several databases, with similar functionality to ODBC/JDBC. We are

Re: [sqlite] connection-specific user data in extensions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/22/2010 06:58 PM, Chris Wolf wrote: >> Hmm, if you mean apsw, Yes, I did. (I'm the author of APSW if that wasn't clear.) >> that's actually one of the things I wanted to >> do: change the >> Connection signature to accept an already open

Re: [sqlite] virtual tables

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/22/2010 06:59 PM, dcharno wrote: > What are some of the things that people use virtual tables for? Are > there any good example usages? FTS3 uses them. Various CSV extensions do too. With my APSW package I include a virtual table that lets

Re: [sqlite] connection-specific user data in extensions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/22/2010 11:31 AM, Chris Wolf wrote: > Is there a way for me to store one or more pointers to data structures > as user data in a sqlite3 structure (i.e. the "connection")? Nope. It is also a problem if you want to share a connection between

Re: [sqlite] SQLite really SLOW on Solaris?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/20/2010 07:12 AM, Lynton Grice wrote: > On Debian it processes a couple hundred messages per second, on Solaris > using the SAME code it does like ONE message per second. One possible cause is the busy handler but this only applies if you have

Re: [sqlite] How to disable and enable constraints in SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/20/2010 08:33 AM, Chris Wolf wrote: > I tried building your APSW wrapper. It built fine, but running "python > setup.py test" failed: > > ERROR: Verify VFS functionality > --

Re: [sqlite] How to disable and enable constraints in SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/19/2010 05:52 AM, Andreas Mucha wrote: > i have to copy data from some database into an SQLite database. > The fasted way for me would be to copy simply all tables. > To do so i have to disable all SQLite - constraints, copy data > and finally

Re: [sqlite] threads and last_insert_rowid()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/15/2010 04:15 AM, Ruslan Mullakhmetov wrote: > i need to get last insert id in multithreaded app. > I use C API, actually some C++ wrap over it. > if i execute query like " insert into tbl( filed ) VALUES ( 1 ); Select > last_insert_rowid() as

Re: [sqlite] SQLite doesn't recognize newly added table

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/13/2010 04:47 PM, Madhan Kanagavel wrote: > I am cross-compiling the standard SQLite amalgamation 3.7.3 using GCC 3.4.4 > on > Linux for a MIPS big endian system. The cross-compiler uses uClibc as the > standard library. I'd suggest trying

Re: [sqlite] improvement for the shell

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/12/2010 04:46 PM, Dave Dyer wrote: > The standard shell behaves very badly if you accidentally > select some BLOB data or excessively long strings. I recommend > this change: You are free to change your copy and to redistribute that change in

Re: [sqlite] Constraint name?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/12/2010 10:04 AM, Petite Abeille wrote: > Thanks for that. Since 2006? High priority indeed :) That the ticket averages a small number of comments per year is an indication that perhaps its priority is about right. Many other ticket tracking

Re: [sqlite] uncertainty how load_extension is supposed to work

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/12/2010 09:08 AM, Chris Wolf wrote: > If so, does that mean we can't use the out-of-the box shell and must > re-compile with a 'C' code change to invoke this? If that's true, why wasn't > this > simply controlled via an environment variable?

Re: [sqlite] Question about SQLite features.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/2010 06:26 AM, jeff archer wrote: > The overall design and structure of applications using SQLite and > therefor SQLite itself would benefit from SQLite supporting stored > procedures. SQLite includes mechanisms to implement almost

Re: [sqlite] Constraint name?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/2010 09:40 PM, Roger Binns wrote: > A ticket that has been open on this topic since January 2006. Oops, forgot to paste: http://www.sqlite.org/src/tktview?name=23b2128201 Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (

Re: [sqlite] Constraint name?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/11/2010 11:12 AM, Petite Abeille wrote: > Is there a way, short of parsing the original DDL, to retrieve a constraint > name? [..] > How does one retrieve the unique constraint name, "foo_uk"? A ticket that has been open on this topic since

Re: [sqlite] Ratio of test code to database code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/10/2010 05:53 AM, Dr. David Kirkby wrote: > Someone recently said he felt that a test:code ratio of 1:1 is about optimal, That of course is bunk. The optimal amount depends on what the project does, the resources available, the consequences of

Re: [sqlite] C Extensions to SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/04/2010 03:35 PM, Barton Torbert wrote: > We are thinkng about writing C Extensions to SQLite to do this. But I was > wondering if there are a set already written that could be used? Not to my knowledge as every programming language already

Re: [sqlite] How to Online Backup In-Memory DB with SQL?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2010 11:50 PM, zhangzhenggui wrote: > If sqlite also provide SQL to do this, it will bring more convenience for > some > scenarios, The problem is that the backup process can return busy/locked errors. With C code you can then decide what

Re: [sqlite] Slow SELECT Statements in Large Database file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/29/2010 10:48 AM, Jonathan Haws wrote: > We have a whole ton of points (3600^2) and a single select returns a single > point - though I may modify the select to return the four corners of the box > corresponding to the point that was entered.

Re: [sqlite] Fw: sqlite3 support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2010 11:47 PM, lizhe wrote: > I am writing to enquire about a bug we found. http://www.chiark.greenend.org.uk/~sgtatham/bugs-cn.html > I would like get support for SQLite ? You will need to do what the page above says in order for

Re: [sqlite] Problem dumping a single line ot UTF8 text into a table (likely a n00b problem)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2010 08:58 AM, Drake Wilson wrote: > Quoth "J. Bobby Lopez" , on 2010-10-28 11:48:12 -0400: >> Another think that crossed my mind is that maybe I haven't set up the >> database properly to accept UTF8 or UTF16 data, but I

Re: [sqlite] Loss of Binary Data in Dump File

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/27/2010 02:20 PM, Art Age Software wrote: > I guess the next question is how do I force the affinity to "blob" The affinity is the type that SQLite will make a reasonable attemp to convert to for that column, but leave the value as is if the

Re: [sqlite] Loss of Binary Data in Dump File

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/27/2010 11:48 AM, Art Age Software wrote: > New to this list and hoping someone can help. I have a sqlite3 > database that contains a couple of tables that have binary data in > BLOB columns. Note that there is column affinity, but the data

Re: [sqlite] programmatic way of determining fragmentation?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/21/2010 12:32 AM, Dustin Sallings wrote: > Mostly, I want to have an idea how fragmented I am. You'll need to read the docs on the file format: http://www.sqlite.org/fileformat.html http://www.sqlite.org/fileformat2.html - From that

Re: [sqlite] create_function_v2 destructor bug or doc issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2010 06:18 AM, Richard Hipp wrote: >> All the other SQLite interfaces with destructors >> (sqlite3_create_module_v2(), sqlite3_bind_text(), sqlite3_bind_blob(), >> sqlite3_result_text(), sqlite3_result_blob()) also invoke their destructors >>

[sqlite] create_function_v2 destructor bug or doc issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The destructor is documented to be called "when the function is deleted, either by being overloaded or when the database connection closes". However it is also called if the create function call fails which took some valgrind runs and reading the

Re: [sqlite] Create Read-only Database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/10/2010 02:55 PM, Bob Keeland wrote: > but there are cases in which the user will, in the vast majority of cases, > not have the knowledge to update the database. None of what I wrote has *anything* to do with users. It was entirely

Re: [sqlite] Create Read-only Database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/10/2010 11:53 AM, Max Vlasov wrote: > Also if you're not content with this option, you can always open the file > (just as a general file) prior to sqlite with a "deny write" option. I'm > aware of such feature in Windows/Win32, I'm sure a

Re: [sqlite] SQLite working with C++'s iostream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2010 10:01 PM, Max Vlasov wrote: > On Sun, Oct 3, 2010 at 7:21 PM, Roger Binns <rog...@rogerbinns.com> wrote: > >> >> Also note that xTruncate may be called to make a file longer. >> >> > Roger, are y

Re: [sqlite] SQLite working with C++'s iostream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2010 10:03 AM, Pierre Krieger wrote: > For example a stream which handles a simple ROT-13 "encryption" can > be written in ten minutes (if you know the internals of the iostream library) My Python wrapper has this functionality as an example

Re: [sqlite] SQLite working with C++'s iostream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2010 09:31 AM, Pierre Krieger wrote: > Anyway I don't think about using this code in a real program for the > moment, I just made it because of my love for modularity and because it > looked like a nice idea It is a good idea and the use

Re: [sqlite] SQLite working with C++'s iostream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/2010 12:25 AM, Pierre KRIEGER wrote: > I made my own implementation You claim that documentation is missing. Specifically what was not documented? BTW for SQLITE_GET_LOCKPROXYFILE just Google "sqlite SQLITE_GET_LOCKPROXYFILE". You should

Re: [sqlite] errors after sqlite3_step

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/02/2010 02:01 PM, Dave Dyer wrote: > Not trying to blame anyone here, just to gather information and ultimately > find a reliable solution. Your reliable solution is to not use networked filesystems with SQLite. Alternatives are using a

Re: [sqlite] errors after sqlite3_step

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/02/2010 12:11 PM, Dave Dyer wrote: > Neither of these fits the scenario, which is multiple readers > contending for access to a networked disk. See the second paragraph of http://www.sqlite.org/faq.html#q5 People have repeatedly found that

Re: [sqlite] Pivot Sequential Data into Dynamic Groups

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/30/2010 02:44 PM, Jordan Dahlke wrote: > Is there a good way to do this with Select and Group By statement? Look in the archives for this mailing list. There was exactly that discussion yesterday with a subject of "Vertical -> Horizontal

Re: [sqlite] grouping inserts vs. one large tranaction

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/18/2010 01:45 PM, Erik Fears wrote: > but I've found that during a write transaction readers are locked from > reading the database. I suggest reading the following two pages: http://www.sqlite.org/lockingv3.html

Re: [sqlite] Automatic index detail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/15/2010 08:58 PM, Cory Nelson wrote: > This might not be doing what you think it is. It does exactly what I think it does and as is documented. > When you have a query that will do a full table scan multiple times, > SQLite can sometimes

Re: [sqlite] Automatic index detail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/15/2010 06:00 PM, Cory Nelson wrote: > SQLite doesn't support automatic indexing, And your basis for that claim is? The basis of mine is that it did for me. And this page: http://www.sqlite.org/optoverview.html#autoindex And these

[sqlite] Automatic index detail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've got a large third party data set I imported into SQLite. Queries are surprising fast especially since I haven't created any indices yet. The reason turned out to be because of the automatic index functionality. When doing an "explain query

Re: [sqlite] SQL Logic error for in-memory database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/15/2010 11:53 AM, Hemant Shah wrote: > The error occurs while calling sqlite3_step(). Call sqlite3_reset and then get the error message text. Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with

Re: [sqlite] DB file locked when no other process using it - Found word(s) list error in the Text body

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/15/2010 01:43 AM, Nick Shaw wrote: > I assume sqlite should no longer have any handles > open to the database; however Windows (which I'm running under) may well > still have open handles to the file waiting to flush cached changes to > disk.

Re: [sqlite] SQL Logic error for in-memory database

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/14/2010 07:41 PM, Hemant Shah wrote: > Sometimes I get following error: > > SQL logic error or missing database. That text corresponds to the error code SQLITE_ERROR which is the code used for a wide variety of error conditions that don't have

Re: [sqlite] Importing csv to SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/13/2010 04:06 PM, BareFeetWare wrote: > All this talk of replacing multiple commas with pipes, then replacing pipes > and so on, though clever and helpful is problematic, cumbersome and even > comical for a mature product like SQLite. SQLite

Re: [sqlite] Backing up SQLite file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/10/2010 01:11 PM, Josh wrote: > A saw the backup API's but they looked overly complicated for my situation. How so? There is sample code at this link (see the second example specifically): http://www.sqlite.org/backup.html It is at most 10

Re: [sqlite] Create a GUI for interacting with a test questions sqlite db

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2010 12:21 PM, Arthur Avramiea wrote: > The pass doesn't have to be in plain text in the software ... I > can store it as sha1 or other kind of hash. Wouldn't that solve most of it? > Or some implementation of SSL. You are confusing

Re: [sqlite] Create a GUI for interacting with a test questions sqlite db

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/05/2010 02:17 PM, Arthur Avramiea wrote: > The sqlite db will be encrypted with http://www.zetetic.net/code/sqlcipher > so that the users of the application without the proper credentials will not > be able to see or modify them. The last part

Re: [sqlite] 64 bit soft heap limit feature request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/05/2010 12:15 AM, Dave Toll wrote: > I do not > understand why there is an assert towards the end of > sqlite3_initialize() that fails on a 32-bit platform if SQLITE_DEBUG is > defined (code taken from SQLite 3.6.23.1): [...] > Am I missing

Re: [sqlite] 64 bit soft heap limit feature request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/03/2010 02:26 AM, Mark Spychalla wrote: > Having the option of using a value beyond 2GB would be > useful for these newer systems for the very same reasons that having a > soft heap limit of up to half the RAM on a system was useful on older >

Re: [sqlite] Detecting storage class from C

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/02/2010 06:52 PM, Andrew Wood wrote: > Yes but none of those functions return the class that the declared type > maps to (SQLITE_TEXT, SQLITE_FLOAT etc), they just return the SQL type > as a string, of which there are umpteen possibilities. >

Re: [sqlite] Pinarejos

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/02/2010 03:28 PM, Vicente Minguez Gzbarda wrote: > Hello good first introduced me in this mailing list, I'm new here. I > wish somebody would help me with SQLite for S60 Nokia phones. Thanks in > advance and greetings to everyone.

Re: [sqlite] Suggestion for project: Chat

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/24/2010 09:51 PM, Artur Reilin wrote: > I thinking about coding a chat with sqlite. The hard part of implementing chat is not storing the messages, but rather dealing with all the clients at the same time especially with potentially hostile

Re: [sqlite] database writes by multiple processes (on a very old computer)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/23/2010 08:21 PM, Chad Rebuck wrote: > I am new to databases so perhaps there is something very basic I am > overlooking here. You may inadvertently be causing the busy errors yourself. Have you read this:

Re: [sqlite] BINARY type

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/19/2010 07:31 AM, Benjamin Peterson wrote: > I was curious if there's a reason why BINARY as a column type doesn't produce > a > column without a type affinity like BLOB. This would be one less special case > between SQLite and other RDMS. The

Re: [sqlite] SQLite Command Line Shell.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2010 10:28 PM, Kirk Clemons wrote: > I would like to be able to tell SQLite that if line 2 is bad just skip to > line 3 and so on until the database has been parsed all the through > maximizing the amount of data I retain. It would require

Re: [sqlite] Will sqlite3_shutdown() in one web page affect the other web page threads?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2010 12:12 AM, Rosbicn wrote: > ... sqlite3_initialize() ... sqlite3_shutdown() ... Why are you calling these functions - ie what do you hope to achieve? Unless you are in a very small device, or doing behind the scenes infrastructure, or

Re: [sqlite] Backup API, .backup command, and writing to handle live backups?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/08/2010 09:17 PM, David Barrett wrote: > Right now I'm just doing a copy of the live file and then running .dump on > the copy, I suggest you use the backup API which will handle all your issues. The way it works is that you start the backup

Re: [sqlite] threading error in sqlite 3 in python

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/04/2010 11:39 AM, Chris Hare wrote: > I have 3.6.12 in use. So how do I get around this error message> It > prevents part of my code from executing Easy - do no create SQLite objects (connections, cursors) in one thread and use them in

Re: [sqlite] Repairing a Database.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/02/2010 07:42 AM, Kirk Clemons wrote: > I have seen some information on repairing a corrupt database and recovering > at least some of the data. But I have not had any luck finding out how to do > it. You can use .dump in the shell. It does

<    2   3   4   5   6   7   8   9   10   11   >