-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Teg wrote:
> I do that fairly often in my program, I've found performance wise it's
> better to just load them up. Even to use a thread to load them and
> post partial results to the GUI so, the loading's dynamic. 10-60,000
> items can be efficiently d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emerson Clarke wrote:
> I have to admit i am a little dissapointed. As the primary author of
> the software i would have thought that you would have a good
> understanding of what the thread safety characteristics of your own
> api were.
He does! It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> So "release" in
> the SQLite and open-source world means something very different than
> "release" for commercial software. In the commerical world, the changes
> are unavailable until released. For SQLite, a release merel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerry Snyder wrote:
> The wiki is there and open to all.
>
> I look forward to reading your additions to it.
To be fair, only some of the documentation is in the wiki. The
remainder is generated. For example you can't edit any of the pages
listed u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I found what appears to be a problem when using prepare_v2 and there is
a SCHEMA error that makes it do a re-prepare.
Firstly I want to confirm that this is a valid way of re-using a statement:
sqlite3_prepare(.. stmt ..);
sqilte3_step(stmt);
sqlite3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> http://www.sqlite.org/cvstrac/tktview?tn=2154 and
> http://www.sqlite.org/cvstrac/chngview?cn=3576
>
> Version 3.3.10 is nigh upon us. Prior to then, I appreciate any
> testing you can do with the latest code out of CVS.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Binns wrote:
> [EMAIL PROTECTED] wrote:
>> http://www.sqlite.org/cvstrac/tktview?tn=2154 and
>> http://www.sqlite.org/cvstrac/chngview?cn=3576
>
>> Version 3.3.10 is nigh upon us. Prior to then, I appreciate any
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Sprenkle wrote:
> I've heard this too. Windows networking has some issues with locking.
> You might research 'oplocks' or 'opportunistic locking' (or
> opportunistic caching)
> if you're interested in understanding what it's doing. I was reading
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Sprenkle wrote:
> How is the first client 'contacted' and asked to respond?
> I can't see how this is anything but useless. I can't imagine very many
> programs honor this kind of request since I've never even heard of this
> before last week. If t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Sprenkle wrote:
> This sounds exactly like what
> causes the trashed shared MS Access databases I've seen and network locking
> issues I see warnings about here.
No it isn't.
> How is this supposed to work correctly without the client being noti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Önnerby wrote:
> So what you are saying is that opening a SQLite DB on a shared network
> drive SHOULD work with multiple clients (if all servers and NFS-version
> are updated to most recent version)?
No, I am stating that the claim in the orig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Önnerby wrote:
> So what you are saying is that opening a SQLite DB on a shared network
> drive SHOULD work with multiple clients (if all servers and NFS-version
> are updated to most recent version)?
Yes. However the locking implementations a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Sprenkle wrote:
> So it sounds like turning them off ( they mentioned a windows registry
> change in
> one web page ) would be a good idea if you wanted to ensure database
> integrity
> on a shared directory.
Oplocks have no effect on database in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Stanton wrote:
> An elegant explanation. Write a book about it!
Chris Hertel already did. This is the bit about oplocks:
http://ubiqx.org/cifs/SMB.html#SMB.10.1
The index has pointers to a few other places where oplocks are discussed.
Roge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SQLite works fine on 64 bit platforms. In my case I am using Linux
64bit. The warnings are about pointers being cast to int.
> Looking at the code, there are pointer to int truncations
> everywhere,
Pointers are used as placeholders in callbacks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Frosst wrote:
> seems that Microsoft's compiler maintains int as 32 bit, while from what
> I'm
> reading, gcc and it's brethren compile it as 64 bit.
On all popular 64 bit platforms, int is 32 bits. On Windows 64 bit,
long is also 32 bit, but 64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexey Pechnikov wrote:
> Is any way to repair corrupted database?
- From a theoretical point of view the only way to repair a corrupted
database is if there are multiple redundant copies of data or of
generating that data. Since SQLite doesn't do t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexey Pechnikov wrote:
> May be on FS layer?
I specifically said VFS which is SQLite functionality - see
http://www.sqlite.org/c3ref/vfs.html and
http://www.sqlite.org/c3ref/io_methods.html
> Which FS can help me for this? I'm using ext3 FS now on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexey Pechnikov wrote:
>> Maybe sqlite3_trace() or sqlite3_profile() can help with what you're
>> looking for here.
Unfortunately sqlite3_trace isn't that useful as it only tells you the
text of the sql statement but not any bound parameters. The wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Dyer wrote:
> While discussing possible sqlite applications today, it occurred to
> me that you could present a sqlite database as a mountable file
> system.
That is relatively trivial to do using FUSE on systems that support it.
> One of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon, Nicholas (UK) wrote:
> I have a table with first_name and a last_name column. I would like to
> find similar duplicates
BTW there exists a whole algorithm for doing this with part influenced
by the medical industry (matching patient records)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> I was looking for precompiled SQLite binaries for WinCE on the download page,
Why do you need the binary? If you use the amalgamation (a single
source file which includes the WinCE support) then you can just add that
source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Of course I could set up a development tool just to compile the SQLite
> source, but it is some seemingly unnecessary extra work. Also I would not
> know where to start.
As far as I know, DRH builds the download binaries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Simon wrote:
> Is this a bug? Or do I need to compile the source differently than what the
> README file directs?
The chances that you found a bug in SQLite that noone else nor the test
suite nor valgrind has hit is vanishingly small :-)
> sqli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey Becker wrote:
> Cool. I'm actually working on extending Robert Simson's ADO.Net
> provider to allow vfs implementations to be written in managed code.
I'm doing the same in my Python wrapper for SQLite (APSW). One feature
I have implemented
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julian Qian wrote:
> I would like us to understand the write patterns of Sqlite.
It looks like the 4 bytes is some sort of header for each database page.
Your trace seems to be of the Android emulator rather than your
application (there are no syncs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> I'm attempting to wrap SQLite with Managed C++ and I'm getting some
> compiler warnings as the compiler/linker is have trouble finding the
> declaration of the structure 'sqlite3_stmt', I've tried looking for it
> manually but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> In the process of upgrading to 3.6.1 I've run into the error on line 46
> of util.c about int sqlite3IsNaN(double x) not behaving consistently
> with the GCC -ffast-math compiler option (which we have enabled), is
> there any al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Background: Will 64 bit versions of SQLite buy us any significant
> difference in performance?
You need to have some benchmark code first, ideally in the form of a
representative script to feed to the sqlite shell. That way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gilles Ganault wrote:
> I need to write an application to manage appointments. Most of them
> are recurrent, with no end-date, while others are one-shots, and the
> user must be able to schedule reccurent appointments but be able to
> tweak some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hardy, Andrew wrote:
> What's the most efficient way of getting a log file of the db activity
> on your sql db over a time period. Can you get timings against these
> acrtivities?
You have to write code/callbacks that interface with the library.
sqli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hardy, Andrew wrote:
> Do I have to pass function pointers (for functions that implement the
> appropriate logging) to these functions (the ones below) then my
> functions get called back omn the appropriate activity?
Yes, those functions are to regi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken wrote:
> Core dump backtrace, using sqlite3 version 3.6.2...
> Suse Linux, gcc 4.2.1
>
> Any ideas?
By far the easiest way of diagnosing is to run valgrind.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIwHbmmOOf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hardy, Andrew wrote:
> How ever the elapsed time in the profile always shows zero.
>
> Does any one have a guess at what I may have left out?
The granularity of the timers on your operating system is greater than
the amount of time it took to execut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ken wrote:
> Sqlite version 3.6.2, Amalgamation
> Backtrace from an abort (6)
You have memory corruption. valgrind will help you figure out the
problem. A backtrace from after memory is corrupted isn't helpful :-)
Roger
-BEGIN PGP SIGNATU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Simpson wrote:
> To me this seems like an obvious bug in Vista,
Actually I'd argue that it is behaving as designed. Generally
filesystem code will try to detect what is going on under the hood. In
particular if it looks like you are doing seq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Simpson wrote:
> The purpose of a cache is to improve performance and responsiveness. Any
> cache that uses all physical memory, forces all other apps to the paging
> file
All current operating systems do this, using heuristics to determine h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Williams wrote:
> Have you ever actually used a version of Windows?
Windows 1.0 (once), Windows 2/286, Windows 3, 3.1, 3.11, 95, 98, ME,
2000, XP, 2003 and Vista.
> ANY OS that attempts to read in a xGigibyte file into real memory to the
> detri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Simpson wrote:
> Ideally, at least on non-CE platforms, I'd like see SQLite not give the OS
> any hints about caching. However, I'm not sure what kind of performance hit
> (if any) that would have on Windows. It's already been proven that
> pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> Has anyone tried to replicate this bug on WindowsXP too?
There are two separate bugs here. One is that when Vista is told a file
is used for random access and then there is a lot of file access, it may
use a little too much mem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay A. Kreibich wrote:
> SQLite is not "lying." After poking around a bit to refresh my
> understanding of SQLite's file structure, I think it is safe to say
> that SQLite will almost never do a sequential file read, even if
> you're doing a s
Mohit Sindhwani wrote:
> Bogusław Brandys wrote:
>> Silly thought,but could it be related to database file extension ? I
>> mean , is it possible that OS is caching some files depending on
>> extension like it was with Windows XP system restore "feature".
>> I know it is almost impossible in thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> The EXPLAIN QUERY PLAN keyword works, and I love it, but it's
> completely undocumented. How come?
http://www.sqlite.org/cvstrac/wiki?p=QueryPlans
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gavin Kistner wrote:
> Mostly I'm sharing this as a curiosity, though I'm quite interested if
> anyone has a suggestion on why
> this might be so much slower on a roughly equivalent machine differing
> only in OS.
See points zero and five at
http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mariano Martinez Peck wrote:
> I CANNOT USE LAST SQLITE VERSION!!! I need 3.4.2
Why?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFI2xGEmOOfHg372QQRAu5QAKCgWWKTlTMubRNUS+aV7HrP0NFx4wCg3q6l
yX9srxlIqSGVZXRYUTTqpj4=
=MWL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mariano Martinez Peck wrote:
> I cannot use the last version because I do not use sqlite directly, but
> through openDBX (http://www.linuxnetworks.de/doc/index.php/OpenDBX). I have
> openDBX working with sqlite 3.4.2 (in linux) but have problems with t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
junkJon wrote:
> here is how I close my DB:
>
> void MySqlite::Close()
> {
> sqlite3_stmt *stmt;
> while((stmt = sqlite3_next_stmt(m_db, 0)) != 0)
> {
> sqlite3_finalize(stmt)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Easton wrote:
> An up arrow just produces the characters ^[[A
The command editing is performed by the readline library. If you
compiled SQLite yourself then you need the readline development files
(includes, libs etc) installed before running co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan wrote:
>http://www.sqlite.org/faq.html#q17
Just for the record, compiling with GCC on 64 bit Linux with -Wall
results in about 20 'variable may be used uninitialized in this
function', although I believe they are all because the compiler doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kristoffer Danielsson wrote:
> However, if it turns out that parsing the VM-structure is incredibly hard,
The "vm structure" is actually byte code for a virtual cpu (one that
happens to be incredibly effective at dealing with the underlying
details o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Burgmer wrote:
> How can I find out if and how it is available to me?
Currently the only way I can see is using public apis/SQL is to try and
create a fts3 virtual table.
> I checked both website (and wiki) and mailing list, but can't find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Listman wrote:
> anyone see a problem with us piggy backing on the svn sqlite
> client install?
You should be asking the Subversion folks. I'd assume they would want
you to ensure your tables have their own namespace prefix. You will
also want to f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathon wrote:
> I am interested in writing my own tokenizer for sqlite3. I've gone through
> Google, as well as the sqlite documentation and unfortunately, I haven't
> found anything helpful.
See the source directory
http://www.sqlite.org/cvstrac/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fin Springs wrote:
> Under what circumstances could one expect to get SQLITE_SCHEMA back
> from sqlite3_exec()?
When using the sqlite3_prepare_v2 api, SQLite attempts to reprepare
statements five times when the schema changes(*). In theory another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zbigniew Baniewski wrote:
> How one should handle this? SQLite has UTF-8 by default.
You seem to doubt being all Unicode is a good thing :-) Read this
http://www.joelonsoftware.com/articles/Unicode.html
> What C-function (Linux) could be considered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guenther Schmidt wrote:
> when I use inserts through prepared statements on windows with ODBC
> all text field values are messed up.
Either the values you supply to the ODBC driver, or the ODBC driver
itself is at fault (most likely the former). (SQL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan Burkitt wrote:
> Maybe a way of making the sqlite3 shell treat these fields as BLOBS,
select cast(column as blob)
You have the full source to the shell and can change the text printing
routine to do whatever you want (hex output, html style es
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan Burkitt wrote:
> Roger Binns rogerb-at-rogerbinns.com |Sqlite| wrote:
>> select cast(column as blob)
>
> I'm glad to know this syntax, but no dice. The nulls seem to be
> insurmountable barriers.
That is due to the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Williams wrote:
> (FYI, Evolution has/had a separate performance problem in that it opens
> a SQLite3 DB handle for the same DB every time you open a mail folder,
> whereas it could just re-use an existing open DB handle.)
Why is that a proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias Müller wrote:
> Is there a way to limit the size of the journal and temporary files created
> and filled by SQLite? Or is it possibly to find out the current file size of
> the journal and tempoarary files using some API.
You can write your o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yoky wrote:
> I create a table include about 200 columns,
http://en.wikipedia.org/wiki/Database_normalization
> like "insert into tablename (Field1,Field2,Field3,...) values
> (Value1,Value2,Value3.)" ,and it's length is more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Da Martian wrote:
> Regarding using "Case" I didnt know sqlite supported this. In fact looking
> at core functions on the web there isnt any mention of a case statement, nor
> in aggregate functions.
Case is not a function but rather an expression. Y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tobias Müller wrote:
>> For an even smaller footprint change, you can write your own
>> xFileControl routine and then use sqlite3_file_control to
>> query/set values.
>
> By "write your own xFileControl routine" did you mean that we should
> change th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MikeW wrote:
> Wondering if there was a way to prevent the FTS3 source getting built,
> I looked at the source to find that it would *not* get built if
> SQLITE_CORE was defined.
SQLITE_ENABLE_FTS3 is what is supposed to cause FTS3 to be included. ie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas Williams wrote:
> I've not run Evolution with SQLite3, so I don't know if it shares the
> cache. I'll ask the user in question to check.
You'll need to ask the developer :-)
http://sqlite.org/c3ref/enable_shared_cache.html
I don't know if th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm still feeling my way around sqlite. One thing that would be handy would
> be the ability to generate a scheme (schema?) for a particular database,
That is something you have to do by hand. The formal process for doing
so is known as normalizat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl Lautman wrote:
> Can someone point out to me the syntax error in the following? I've omitted
> the set-up code for brevity, but cur is a cursor with a connection to the
> database. Thanks.
>
x = cur.execute('last_insert_rowid()')
last_i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl Lautman wrote:
> Thanks, Roger. Your second suggestion does the trick. The first, however,
> returns: . Can you explain why?
> Thanks again.
Both pysqlite make the cursor an iterator. Remember that a query can
return zero, one or more rows o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl Lautman wrote:
> E.g. pysqlite's .lastrowid method isn't mentioned at all on pysqlite.org.
Go to pysqlite.org
Click on pysqlite usage guide
All Python database adapters attempt to have the same interface so your
code can (in theory) work with S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Kyngesburye wrote:
> So, sqlite supports UTF8 directly - UTF8 in, UTF8 out.
No. SQLite supports Unicode internally. The APIs let you supply and
receive Unicode strings in UTF8 and UTF16. The actual encoding
serialized to disk depends on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MikeW wrote:
> Having looked at the source code, looks like the best way to do this
> /would/ be to add another (!) numerical parameter to sqlite3ErrorMsg()
> indicating
> the extended error code that corresponds with the message.
http://www.sqlite.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pados Károly wrote:
> How could I make it even smaller?
http://article.gmane.org/gmane.comp.db.sqlite.general/24080
http://www.hwaci.com/sw/sqlite/prosupport.html
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
??? wrote:
> As I understood, incremental
> BLOB I/O requires space of constant size to be preallocated
> with zeroblob,
That is correct.
> but I don't know the size of stream in advance.
Then you can't use the incremental I/O for writ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muratet wrote:
> Can someone please tell me where I could start looking for the problem?
You seem to be mixing system supplied SQLite libraries, your own
compiled ones and Python SQLite module. It also looks like you are
using a Mac. The OSX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Clarke wrote:
> Is it really correct that in order to perform an INSERT, Sqlite demands
> that no other connections be active?
http://www.sqlite.org/lockingv3.html
http://www.sqlite.org/sharedcache.html
http://www.sqlite.org/atomiccommit.html
Ro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> Are there any guides to implementing a VFS (sqlite3_vfs) for SQLite? A
> good practices guide would be as useful. I already have an existing
> file system API/library for the target system so I guess it is mostly
> just matchi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> unable to import Sqlite API: No module named sqlite3
You are missing the module that binds Python to SQLite. It comes as
standard with Python but is only built if SQLite is already on the
machine. Chances are you can find
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muratet wrote:
>> The image in the directory is version 3.6.4, but the image that gets
>> installed is 3.3.6. How can that be?
Best guess is that the shell binary is from 3.6.4 but the shared
libraries it picks up are 3.3.6. Run `ldd /usr/l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brown, Daniel wrote:
> Is it possible to change the VFS SQLite is using while SQLite is
> running?
You can call sqlite3_vfs_register/unregister at any point. Note that
SQLite does no inuse tracking so it will happily let you unregister a
VFS current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Clarke wrote:
> So one can share one open raw database connection across multiple threads can
> you?
That is true in theory but there are some issues in practise. For
example there is currently no thread safe way to get error messages
(being ad
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muratet wrote:
>> [EMAIL PROTECTED] src]# ldd /usr/local/bin/sqlite3
>> linux-gate.so.1 => (0xe000)
>> libdl.so.2 => /lib/libdl.so.2 (0x00c5a000)
>> libc.so.6 => /lib/tls/libc.so.6 (0x00af3000)
>> /lib/ld-linux.so.2 (0x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muratet wrote:
> I built sqlite
> from the aggregate code but my python project hangs.
There is a specific mailing list for Python with SQLite - see
http://itsystementwicklung.de/cgi-bin/mailman/listinfo/list-pysqlite
> So, I tried to
> use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Avinash Mittal wrote:
> Is there any roadmap made for SQLite?
What specifically do you find missing?
> I couldn't found any specific things on wiki or any othere site.
You can track the changes to the code, wiki and tickets here:
http://www.sqlite.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Muratet wrote:
>> I guess I'm not making my myself clear. I only have one installed
>> version.
That is not true. If it was true then you wouldn't have ended up with
3.3.6 being reported as a version in places! You may think you only
have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> Thanks for help, But I could not get the point, should I again rebuild the
> python, as this time it will build sqlite3 module also because now SQlite
> is already present on the system.
> Is there any other way by which I ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
raf wrote:
> the sqlite3 .dump command (version 3.4.2 and earlier) often fails
> silently. i.e. it produces a file containing nothing but:
The code for the shell mostly just runs sqlite3_exec and often ignores
the return code (unless it is SQLITE_CORR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas E. Fajardo wrote:
>( To the 'powers that be'... I wonder if some form of 'cache' for prepared
> statements might be built in to the 'sqlite3_prepare*' functions as a
> performance enhancement? )
I couldn't find an existing ticket so crea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
> The atomic write size on the system file hosting my database is limited by
> design to 32Kbyte. I want to verify that SQLite will never write more than
> this amount.
You can make your own VFS where you can return the atomic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
raf wrote:
>> printing error messages to stderr rather than ignoring
>> them shoulden't require an overhaul.
It does though. You need to fix every place where an error can be
detected and take an appropriate action. One extra printf is not the
entir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan wrote:
>> http://www.sqlite.org/cvstrac/tktview?tn=3483
>
> Are there advantages to implementing this internally instead of
> externally?
Firstly there is an advantage to having a statement cache. I use a
benchmark based on
http://www.sqlite.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Stanton wrote:
> Perhaps this featrure could be reserved for "Sqlheavy", a replacement
> for Oracle.
Or a #if OMIT_STATEMENT_CACHE like all sorts of other functionality that
can be omitted.
> We have actually implemented the cacheing of prepare
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kees Nuyt wrote:
> Did you try
> .bail on
> It won't change the destination of error messages, but at
> least it aborts the sql script at the first error it
> encounters.
That is not true of errors returned by sqlite3_exec when doing .dump.
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas E. Fajardo wrote:
> John Stanton has correctly pointed out that there is a programming model here
> an application
> effectively does the cacheing itself by precompiling statements at startup.
> In this situation,
> the proposed cacheing fe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yoky wrote:
> I create a table with 200 columns,
If you have that many columns but want queries with only some of them,
then it is a good indication that your schema is not normalized. See
the wikipedia entry for some guidance:
http://en
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
henry wrote:
> The problem is the next time
> when I connect the Sqlite, the actions I did last time has all gone
> away, it did not take any effect to the database. There's no error code
> when using the sqlite api, and if I use that handler to query
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
钱晓明 wrote:
> I want to store image data into sqlite by spliting image to many
> blocks(256*256pixels).
Why are you splitting it? You can use the incremental blob api for
access http://sqlite.org/c3ref/blob_open.html
> The table has the 32K page size
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Avinash Mittal wrote:
> I have built a rpm package for SQLite-3.6.4, now i want to do self test for
> the package.
It is best to do the testing during the build process as it needs
alternate compilations of the source (for example to do fault
injecti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
RanRan wrote:
> I have a program that would create a child process.
http://www.sqlite.org/faq.html
Question 6, last paragraph.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkc+lYACgkQmOOfHg372QQOWgCeLkoxrDl8Xt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Avinash Mittal wrote:
> I think compiler is not getting tcl.h file
>
> Now what should be done to debug these errors
Make sure the TCL development files (headers and libraries) are
available. If you don't know how to do that then you need to contact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
RanRan wrote:
> In the child process, I closed the database and opened a new one for the
> child process to use. Won't it fix the problem? Thank you so much again.
No, because after the fork both the parent and the child have the
database open. There
301 - 400 of 1461 matches
Mail list logo
