Re: [sqlite] [solved] SQLite won't import 53, 066, 244 row 11 gigabyte CSV file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > On 28 Nov 2009, at 3:55pm, Walter Dnes wrote: > >> ...and import worked. So it appears that the maximum csv file is probably >> around 2 gigabytes. > > That does make sense of some kind, but it indicates that someone is using

Re: [sqlite] SQLite won't import 53, 066, 244 row 11 gigabyte CSV file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Walter Dnes wrote: > Am I making some glaring noob error here? The most likely cause is that the SQLite shell was compiled without support for large files. (The SQLite library itself has large files on by default but the shell is separately compile

Re: [sqlite] advantages of Not using shared cache mode

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Rivera wrote: > In trying to understand shared cache mode, I would like to know why one > would Not use it. It is not useful unless you open the same database multiple times concurrently within the same process. Then it only saves you time a

Re: [sqlite] Corrupted SQLITE database recovery

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Griggs, Donald wrote: > You may want to try >.dump mytable1 >.dump mytable2 >etc > On individual tables to see if some are salvageable. That is what the underlying dump code does anyway. > For failing tables, if you *can* read a certain n

Re: [sqlite] Set error message within virtual table implementation?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 wcl...@gfs-hofheim.de wrote: > Is it possible / can it be possible to set the error message (as would > then be read by a call sqlite3_errmsg) from within a virtual table Yes, see the zErrMsg member: http://sqlite.org/c3ref/vtab.html If non-null

Re: [sqlite] another Feature Request: char from codepoint?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Romano wrote: > The requirements for the flip() function I've requested are unambiguous: > simply reverse the string, raw codepoint by codepoint. My point was that your requirements are that, yet someone else wanting a "flip" function could wan

Re: [sqlite] does there some fts3 document i can read

ouwind wrote: > i cant find documents about fts3 in sqlite documents http://www.sqlite.org/cvstrac/wiki?p=FtsUsage Roger ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] another Feature Request: char from codepoint?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Romano wrote: > I would hope that it could be included by default. [Note I do not speak on behalf of the SQLite team but have been an observer for many years] Your request is extremely unlikely to go into the SQLite core as the bar is *very* hig

Re: [sqlite] Suggested user-defined-function example

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Walter Dnes wrote: > It didn't help me because it used only one parameter. It didn't say > anything about you > - *MUST NOT* have commas between parameters in the function definition That is standard TCL rules and has nothing to do with SQLite. >

Re: [sqlite] sqlite3_value_type question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > can we rely on testing for the 5 datatypes reliably? Yes, it will only be one of the 5 types. > I understand that when the argument comes from a column, then the type > returned by sqlite3_value_type() is the colu

Re: [sqlite] another Feature Request: char from codepoint?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Romano wrote: > I respectfully disagree, Roger, about the simplicity. Creating an > external DLL would complicate my distribution scenario significantly > because I'll have just as many users of my little database application > working with Ap

Re: [sqlite] another Feature Request: char from codepoint?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > I googled, and there doesn't seem to be a page which describes the abilities > and limitations the extension system has. A C function of your choosing can be called on each new connection being created: http://sqlite.org/c3re

Re: [sqlite] listing free bytes in sqlite files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt wrote: > Given a sqlite database file I would like to create two lists: one of bytes > which are in use and one of bytes which are "free". > What would be the most efficient way to do this? What are you actually trying to achieve? If you are tr

Re: [sqlite] another Feature Request: char from codepoint?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Romano wrote: > This would be a convenient function to have. Are there technical > issues/obstacles? In general for all these feature requests for more functions there is no need for them to be added to the SQLite core. There is a very simple AP

Re: [sqlite] is ticket 4037 not a bug?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bogdan Ureche wrote: > I just noticed the ticket was closed without being fixed, with the following > remark: I was the one who closed it and added that remark. > Now, I have to admit that English is not my first language, nor the second, > but the w

[sqlite] APSW 3.6.20-r1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 APSW is a wrapper around SQLite that provides all SQLite API functionality in Python. It also has an interactive shell so you don't have to use Python. The home page is http://code.google.com/p/apsw/ which includes a changelog. New in this release is

Re: [sqlite] Output in currency format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > JavaScript doesn't have an integer type, just a number type: You are agreeing with me :-) Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYE

Re: [sqlite] Output in currency format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > Integers in all languages I'm aware of are not stored as mantissa/exponent, > they're stored as bits with complete precision. There is one huge exception I found out the hard way recently: Javascript stores all 'integers' as f

Re: [sqlite] Bug candidate: virtual tables vs. external db connections

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grzegorz Wierzchowski wrote: > That was my first suspicion that there is some memmove with cursor object or > so. > This would mean that sqlite* or maybe other sensitive pointers can not be > members of cursor object, what is wrong for me. There is

Re: [sqlite] Bug candidate: virtual tables vs. external db connections

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grzegorz Wierzchowski wrote: > $ diff sqlite-3.6.20-BUG/src/test8.c sqlite-3.6.20-ORIGINAL/src/test8.c > 93d92 > < sqlite3 *pDb;/* Database connection */ > 572,574d570 > < if (pCur->pDb) > < sqlite3_close(pCur->pDb); > < pCur

Re: [sqlite] Understanding database lock

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Akash Rao wrote: > Wanted to understand the sqlite database lock a little better. Read this: http://www.sqlite.org/lockingv3.html Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://eni

Re: [sqlite] db file locked after power loss

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shawn Boyle wrote: > The sqlite3_open() call returns > SQLITE_IOERR. All attempts to copy the db file from the device fail. That indicates your device is having issues. If you can't read the file then neither can SQLite. Roger -BEGIN PGP

Re: [sqlite] Is the dbFileVers written to journal files?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Scott Hess wrote: > Someone was asking me a question about what happens if the wrong > journal file gets applied to a database. My answer was that terrible > things happen. See also http://www.sqlite.org/src/info/61d35ac210 Roger -BEGIN PGP SIGN

Re: [sqlite] Output in currency format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Haworth wrote: > I have a column defined with a type of FLOAT, which I believe is > treated as REAL by SQLite. When selecting that column, I would like > it to be returned with a leading "$" sign and always have a decimal > point and two n

Re: [sqlite] sqlite for threads

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 jeff...@aol.com wrote: > I have a program which uses threads, when writing to (sometime even reading > from) SQLite, I always got the error of database is locked. http://www.sqlite.org/lockingv3.html Roger -BEGIN PGP SIGNATURE- Version: Gnu

Re: [sqlite] UPGRADE to 3.6.20 and python

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cooper, Andrew wrote: > This has probably been asked a lot of times before but I couldn't find > an answer in the archives. You should ask on the python sqlite list :-) It is jointly maintained by the authors of the two Python to SQLite bindings:

Re: [sqlite] Feature Request: Return non-0 from sqlite3 Client on Error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David E. Wheeler wrote: > I'm using -bail with the sqlite3 client, which is great, but alas > sqlite3 doesn't return a non-zero value when it bails with a failure: This was fixed in 3.6.20 most likely as fixing this: http://www.sqlite.org/src/in

Re: [sqlite] Canceling a integrity check in progress (feature request)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Wright wrote: > sqlite3_interrupt does not appear to cancel an integrity check (pragma > integrity_check or quick_check) in progress. http://www.sqlite.org/src/info/33fdaab1a0 Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux)

Re: [sqlite] Find non-numeric character in text field

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 RB Smissaert wrote: > I would like to do a where on a text field and check if the values have > non-numeric characters, > which is in this case is anything other than 1,2,3,4,5,6,7,8,9,0 or a space > character. > Is this possible without using a UDF or

Re: [sqlite] index optimal?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sylvain Pointeau wrote: > how do we know that we are using an optimal index in a query? How do you know if you are not? The point of an index is to avoid visiting every row in a table while evaluating an expression, so generally the best index is one

Re: [sqlite] Roadmap for SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shaun Seckman (Firaxis) wrote: > The SQLite Consortium membership would be great but so far this > newsgroup has answered every single one of my questions within a 2 hour > window of posting..for free! The consortium membership is not about answerin

Re: [sqlite] Roadmap for SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shaun Seckman (Firaxis) wrote: > I'm really interested in finding out what sort of major features or > tweaks are planned to be in upcoming releases (within the next 6 > months). You get what you ask for :-) Have a look at these two pages: http://

Re: [sqlite] sqlite3 commandline interface questions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 waltd...@waltdnes.org wrote: > 4) And to stop the flow of questions, is there a full manual for sqlite3 > somewhere? Whilst looking through Google, I stumbled across the > ".database" command, which I do not recall seeing on the sqlite.org web > site

Re: [sqlite] SQLite on a Windows Network

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > Standard Windows drive sharing uses SMB, sometimes called SAMBA. SMB stands for Server Message Block - the name of the protocol as originally developed by IBM in 1982. The protocol is extensible in that a dialect is negotiated u

Re: [sqlite] How to skip the first field on .import

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Rolle wrote: > How do I let this start out at the default value and auto increment? > My column separator is '|'. Create a temporary table and import into that. Then copy those values into your permanent table using something like: insert into

Re: [sqlite] feature proposal - strong but dynamic typing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > But on a newer SQLite that implements the stronger typing support I proposed, > when that feature is active then columns with declared types like INTEGER/etc > would enforce that only values of that type are stored there, I m

Re: [sqlite] feature proposal - strong but dynamic typing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > I should point out, for people reading this thread, that it is very possible > to > have both the amount of type flexibility that SQLite provides and have strict > typing, at the same time. What I fail to understand with all

Re: [sqlite] Degree character not displayed correctly.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > First decide or determine what is (or shall be) your database > encoding. Even if SQLite has no problem storing ANSI (or EBCDIC or > anything else) strings untouched, This isn't particularly good advice. SQLite w

Re: [sqlite] FTS3 - closed ticket 3950 - bug still exists in 3.6.19

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wanadoo Hartwig wrote: >> Actually, if you replace the FTS3 table with any other type of table - >> or as many tables as you like and do also in these tables insert >> operations - the last row id of the original table is correctly >> returned. T

Re: [sqlite] FTS3 - closed ticket 3950 - bug still exists in 3.6.19

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> can you please re-open the ticket? This bug only occurs in >> combination with FTS3. Using normal tables in triggers does not cause >> any problems. The underlying cause is that FTS3 has several other tables (use .dump to see them) that store its u

Re: [sqlite] Occasional SQLITE_BUSY error on database with read-only operations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pavel Ivanov wrote: > I believe the problem here can be either in buggy file locking via NFS The issue is two fold. One is that SQLite still does locking operations even if you open read only (which may not be expected by some users but is necessary)

Re: [sqlite] Occasional SQLITE_BUSY error on database with read-only operations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jamie wrote: > Given all this, why am I on rare occasions getting a SQLITE_BUSY > return code when calling sqlite3_prepare_v2() or sqlite3_step() ? Hint: How does the SQLite connection you are currently using know that no other SQLite connection won'

Re: [sqlite] SQLite server for Windows/Linux?

Gilles Ganault wrote: > I wanted to check if someone had > recently written a similar solution so that SQLite can be used as a > light, no-brainer DB server? The problem is that the moment you have a network accessible service you have to deal with administration. Things like authentication, secu

Re: [sqlite] Spam filtering. Was: Data migration tool certification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 D. Richard Hipp wrote: > Is there a > different mailing list manager we should consider switching to? What I have found most effective is having the ability to moderate the first posts from new users. That way you don't care who joins but do get to f

Re: [sqlite] manipulating arguments (in C)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > I feel the need to wrap an SQLite printf-like function into a scalar > function. You can just do that sort of thing in your application. There is no need to do it via a SQL function. > My question is slightly off

Re: [sqlite] Questions about sqlite3_result_text*

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > >> You are trying really hard to overthink things :-) > > I simply found version c-1) in a widely spread extension and was > surprised by this way of doing the return, unduly complicated and > inefficient in my po

Re: [sqlite] Questions about sqlite3_result_text*

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > a) is it allowable for a scalar function to modify (in place) an input > argument No. > b) same question for unmodified arguments: is it possible to avoid > duplication > of an argument if the function determi

Re: [sqlite] Why FTS3 has the limitations it does

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wanadoo Hartwig wrote: > It seems to be that ticket 3950 was also closed > (I actually opened this ticket using version 3.6.16). The reason for > closure was that the bug seems to have disappeared It is actually closed. I'm the one who has been go

Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > Could you point me to the test case you referred to? Look near the bottom of the ticket where it lists the various checkins. [6955] is the test case. You can examine the current source in case that has changed at http://sqlite.org/

Re: [sqlite] Using SQLite from Java

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 J. R. Westmoreland wrote: > I looked on the site and didn't find anything. http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers :-) Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enig

Re: [sqlite] Using SQLite from Java

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 J. R. Westmoreland wrote: > Can someone point me to the information on using Java with SQLite? What was not useful in the Google search results you got? Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with M

Re: [sqlite] Ticket 3810: SQLITE_ERROR on concurrent CREATE TEMP TRIGGER and sqlite3_close()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Toll wrote: > The race condition described in http://www.sqlite.org/cvstrac/tktview?tn=3810 > is > still present in SQLite 3.6.19 (amalgamation version running on Linux) My biggest problem with the ticket is the huge list of omits and other defi

Re: [sqlite] "x NATURAL JOIN x" BUG

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kristoffer Danielsson wrote: > When can we expect a bug fix? Days, weeks, months? Go to http://www.sqlite.org/src/reportlist and you can see all open tickets. (Currently there is no report in priority order). SQLite consortium members and paying cus

Re: [sqlite] searching sqlite tickets?

Jens Miltner wrote: > it's still a bit annoying, since I > can't search for existing reports efficiently You are preaching to the choir :-) You can create a bug report about this at http://www.fossil-scm.org (Fossil is being used by SQLite). You can also run fossil yourself and clone the repo

Re: [sqlite] searching sqlite tickets?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Miltner wrote: > In the current sqlite.org website, I can no longer search for tickets > - I can only show all tickets, all closed tickets or all open tickets, > but I can't search for keywords any more... Yes I whined to DRH about that too.

Re: [sqlite] SQLite encription

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > It happened again. DRH explained to me last time I asked. If someone > posts from an address that isn't on this list, there's a delay before > the post shows up because it waits for moderator approval. In the > meantime t

Re: [sqlite] SQLite encription

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Francisc Romano wrote: > Is it possible to encript SQLite databases so that they cannot be referenced > outside the program that uses it? > If not, can you set a user and password for a SQLite database? The answer has not changed from when you asked a

Re: [sqlite] Why FTS3 has the limitations it does

Wanadoo Hartwig wrote: > Slightly different question but related to FTS3. Does anybody know why > this fails using FTS3? It isn't failing. Behind the scenes FTS3 is implemented using 3 other tables (try .dump to see). You are indeed seeing the last inserted rowid. Roger __

Re: [sqlite] reach into a memory database and retrieve a record by it's oid

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Arts wrote: > Is there a (relatively easy) way to hack up a function call that would > just retrieve one record by it's oid (primary integer key), and return it > in a form that would allow using the sqlite3_columm() functions? > > Something along

Re: [sqlite] SQLite encription

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Francisc Romano wrote: > Is it possible to encript SQLite databases so that they cannot be referenced > outside the program that uses it? The SQLite database file has to be accessible to the program using SQLite so no matter what you do, a malicious u

Re: [sqlite] suggestions for avoiding "database locked" on ajax

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 P Kishor wrote: > So, what suggestion might you all have for getting around this? Why not set a busy timeout? Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAR

Re: [sqlite] sqlite .dump does not save PRAGMA user_version

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Schubert wrote: > When creating a dump with sqlite .dump, it will not save the user_version. The problem is that the usage of the user_version is not known. It could be harmless to dump or it could cause problems on a restore. > PS: please CC

Re: [sqlite] SQLite Database connection timeout

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andi wrote: > MySQL has 8 hours connection timeout, is there a connection timeout after > open SQLite database ? What makes you think SQLite has connection timeouts? Hint: read the web site to learn more about SQLite. Roger -BEGIN PGP SIGNATURE

Re: [sqlite] readers and writer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > On 14 Oct 2009, at 7:45pm, Pavel Ivanov wrote: > >> sqlite> .timeout 1 > > What is it that that command does ? I looked for a PRAGMA but didn't > find one. Or does it correspond to a check-and-retry loop which the > pr

Re: [sqlite] readers and writer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > What I will say is this: I see no reason why there > should be more bugs in the AFP locking code than there are in the > locking code that comes into play if you're accessing a file on your > own hard disk. In which case yo

Re: [sqlite] readers and writer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Slavin wrote: > Perhaps this passage could be rephrased to warn explicitly about NFS > rather than about the more general "files on a network filesystem". As a general rule network filesystems are buggy. Local filesystems get to make all the

[sqlite] Small typo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On comment says "Walues" instead of "Values" (do a grep). http://www.sqlite.org/cvstrac/tktview?tn=3849 Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAY

Re: [sqlite] flexible data import

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 P Kishor wrote: > Shame on you Roger Binns, for suggesting CouchDB, because now, it > seems that CouchDB might supplant SQLite as one of my most favorite > pieces of software. It is a great complement to SQLite, and is a better choice

Re: [sqlite] sqlite in-memory database far too slow in my use case (new benchmark inside)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Arts wrote: > Will the amalgamated version be faster > than linking the lib at runtime? The SQLite website quotes a 10% performance improvement for the amalgamation. The reason for the improvement is that the compiler gets to see all the SQLite c

Re: [sqlite] flexible data import

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Poddey wrote: > does there exist some approaches to deal with situations like this? It isn't clear exactly what your question is. You can quite happily add columns to an existing table at any time using ALTER TABLE ADD COLUMN. If each "ent

Re: [sqlite] sqlite in-memory database far too slow in my use case

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Arts wrote: > Using hash tables I can do 10 requests in .24 seconds > meaning around 40 req/sec. If you are just doing simple lookups (eg doing equality on a single column) then a hash table will always beat going through SQLite. But if y

Re: [sqlite] sqlite in-memory database far too slow in my use case

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Arts wrote: > So I am wondering if I can drop the glib Hash Tables, and > go sqlite all the way. But I'm afraid the process of > constructing SQL queries / parsing them by sqlite, and > interpreting the results in my app, multiple times per > event

Re: [sqlite] Will Bitwise Operations Use an Index?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Wickes wrote: > I'm trying to optimise some of my queries, and I would like to know if > bitwise operators in terms will still use an index, SQLite provides you the tools to find out for yourself. In the shell do '.explain' and then give it yo

Re: [sqlite] Problem with PAGE_SIZE and CACHE_SIZE in the sqlite356c-api

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Make a new db-file in the windows explorer. > Open this file in the console with sqlite3 db-file. > Then set the page_size and the cache_size with the pragma statements. You cannot change the page size of a database after it is created(*). When you

Re: [sqlite] Wrong column decltype

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pavel Ivanov wrote: > Changing of declared datatype in CREATE TABLE AS SELECT is intended > and was made in 3.6.15 (look here > http://www.sqlite.org/releaselog/3_6_15.html). It is also mentioned in http://www.sqlite.org/datatype3.html at the end of s

Re: [sqlite] Tedious CSV import question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nuno Lucas wrote: > All I can say is that the virtual table API is still considered > experimental (or was last time i checked), so it's not stable across > sqlite versions Virtual tables were added mid-2006 (SQLite 3.3.7). 3.3.8 had an incompatib

Re: [sqlite] Phoronix SQLite benchmark Improvements - [was Re: SQLite behaviour on FreeBSD and KVM]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Tippett wrote: > 'How do I determine what impact the host os/environment has on sqlite'. The very first test should be a sanity check where you do a bunch of inserts each as their own transaction. Each transaction should require calling fsy

Re: [sqlite] Phoronix SQLite benchmark Improvements - [was Re: SQLite behaviour on FreeBSD and KVM]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Tippett wrote: > Any takers? It isn't clear what you want. It mostly appears to be people to fix the Phoronix test suite. That is really their problem! SQLite already includes various speed tests. For other people the only benchmark that i

Re: [sqlite] SQLite Encryption Extensions(SEE) for SQLite

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Simpson wrote: > I'm pretty sure the license Rather than speculating, the SEE usage and license is documented at http://www.hwaci.com/sw/sqlite/see.html Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuP

Re: [sqlite] How do I get context in collation function?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Christophe Deschamps wrote: > Really, SQLite doesn't have emergency brakes? Not for collations, just user defined functions. It is a bit of a pain to deal with. I have the same issue in APSW but at least I can still report a Python level error

Re: [sqlite] Compile test example problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Morris wrote: > Building sqliteFirst.obj. > Building SQLiteFirst.exe. > POLINK: error: Unresolved external symbol '_sqlite3_open'. > POLINK: error: Unresolved external symbol '_sqlite3_errmsg'. > POLINK: error: Unresolved external symbol '_sqlite

Re: [sqlite] SQLite performance with lots of data

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Francisc Romano wrote: > how big databases SQLite can take, please? Someone told me recently they have 37GB and 66 million rows in their data set. Another user is using the virtual table functionality together with synthetic indices to optimise worki

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Williams wrote: > Oh, I think you meant that the L suffix would break on anything other > than LP64 or ILP64 models. Correct. L means long. On platforms where long is 32 bits, shifting a long value by more than 32 bits will give zero. > I'm

Re: [sqlite] C code spanish character insert problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bible Trivia Extreme wrote: > (loop over spanish .txt file here while inserting) > sprintf(query, "INSERT INTO questions VALUES('%s', '%s')", question, > answer); That is a *really* bad way of doing things, both from a performance point of view and se

Re: [sqlite] SQLite behaviour on FreeBSD and KVM

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthew Tippett wrote: > I would like to highlight the following SQLite benchmark results posted > by Phoronix via Phoronix Test Suite (http://www.phoronix-test-suite.com/) An earlier test showed massive differences for Linux filesystems but those res

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Williams wrote: > On Tue, Sep 29, 2009 at 11:21:30AM -0700, Roger Binns wrote: >> Nicolas Williams wrote: >>> If you move the cast to the left the warning should go away: >>> ((sqlite3_int64)(1L<<63)) >

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nicolas Williams wrote: > If you move the cast to the left the warning should go away: > ((sqlite3_int64)(1L<<63)) And this is why making warnings go away leads to bugs. The replacement above will only work if sizeof(long)==sizeof(long long) which i

Re: [sqlite] building permanently loaded extensions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 P Kishor wrote: > So, here it is again -- how can I convert a loadable extension to a > permanently loaded extension? A tutorial, por favor. Look at how RTree, FTS3 and ICU are done with the amalgamation. Roger -BEGIN PGP SIGNATURE- Version:

Re: [sqlite] feature request - field exclusion list in select list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > The main rationale for the feature I mention is code brevity, For more context, what language are you writing your code in and how do you get the contents of each column. Using the C api there are 3 ways: 1 - Explicit: "sele

Re: [sqlite] feature request - field exclusion list in select list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Darren Duncan wrote: > I was initially going to file a ticket, but it seems that non-registered > SQLite > developers can't do that anymore, and we're supposed to do it on sqlite-users > where a non-registered developer would then distill list chatt

Re: [sqlite] Compiler warnings with Sun Studio 12.1 on Solaris 10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dr. David Kirkby wrote: > "sqlite3.c", line 18731: warning: integer overflow detected: op "<<" > "sqlite3.c", line 18748: warning: integer overflow detected: op "<<" > "sqlite3.c", line 32546: warning: statement not reached > "sqlite3.c", line 69160: w

Re: [sqlite] inserting a number as a string and keeping it that way

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sean Moss-Pultz wrote: > OK. Then I'm going to need to escape this string since the insert is > really coming from a import of a huge datadump generated in Python. You should probably explain the big picture first. Python has at least two wrappers ar

Re: [sqlite] inserting a number as a string and keeping it that way

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sean Moss-Pultz wrote: > How can I get the string to stay 0123? It isn't a string - you supplied an integer and SQLite treated it that way and then stored it. If you really wanted a string then you must quote it (remember to use single quotes). If y

Re: [sqlite] SQLite Suitability for Shopping Cart

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 CityDev wrote: > What that seems to be saying is you can have concurrency but you will suffer > the effects of whole-database locking for update transactions. It seems a > glaring shortcoming, so either SQLite is not normally used by multiple > process

Re: [sqlite] Problem if IF NOT EXISTS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew wrote: > I didn't see a way to search the mail archive, Go to http://sqlite.org/support.html and look in the middle of the page where it describes the mailing lists. All 3 links to archives take you to pages that then have an option to search

Re: [sqlite] Sqlite testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ydlu wrote: > I am Windows CE software developer, so I am really, really want to learn how > you built and test "sqlite3.exe" in Windows CE platform. so I can run a > console command line in Windows CE enivroment. http://www.sqlite.org/testing.html M

Re: [sqlite] Inserting into an empty table

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Barton Torbert wrote: > I am having problems inserting a record into a table that is empty. I get > back an error. Is there any special issues involving this? http://catb.org/~esr/faqs/smart-questions.html http://www.chiark.greenend.org.uk/~sgtath

Re: [sqlite] List of active savepoints names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lukas Gebauer wrote: > You must be very unhappy about current existence of > sqlite3_get_autocommit function, right? You said, by the way: "It is > not needed, if you organize your code well." :D It is the same case! Personally I don't use it since

Re: [sqlite] List of active savepoints names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lukas Gebauer wrote: > I am not creating and releasing savepoints! Yes you are. The SQLite library is not magically doing them on a whim. Your code is asking for them. >> You can create a custom wrapper for savepoints which may have >> the stack o

Re: [sqlite] Most wanted features of SQLite ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > SQLite does have the best extensibility of known to me DBMS. Also not mentioned is that it is available under a public domain license and hence anyone has the right to use it in any way they deem fit, make changes, distribute

<    5   6   7   8   9   10   11   12   13   14   >