-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/31/2011 07:49 AM, Simon Slavin wrote:
> neither of them can enter the new price into the system, they have to each
> enter the price change,
You cannot get conflicts if both "users" are talking to the same server - I
can explain why if you care
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any database system can be nonsensical. If you have multiple people editing
prices for the same item even with a single instance database you can have
the wrong final answer. But that is a procedural and business issue, not a
technological one.
Usin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 11:33 PM, Alexey Pechnikov wrote:
> You write extra code to find and resolve CouchDB replication conflicts but you
> are speak about "do not have to write extra code". One of these
> approvals is false!
Not quite and it was deliberate wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 03:31 PM, Alexey Pechnikov wrote:
> There are no conflicts!
If you have multiple masters then incompatible changes can be made to the
same data.
> Two versions are two _different_ versions of the row.
ie you have a conflict.
> On app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 03:12 PM, Simon Slavin wrote:
> Conflict resolution is so hard it's sometimes impossible.
CouchDB does it well. The vast majority of the time there are no conflicts.
When there is a conflict it picks one contender (something like the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 02:29 PM, Mr. Puneet Kishor wrote:
> could you please tell what this other "JSON database server product" was?
MongoDB.
A major difference between MongoDB and CouchDB is how they store data.
CouchDB uses an append only structure - data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 01:43 PM, Alexey Pechnikov wrote:
> Multi-master replication can be easy with correct data structures.
It takes more than a few lines of SQL. You've also got to be careful how
you write data (result is a DAG), you need replication code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 12:24 PM, Max Vlasov wrote:
> so CouchDB will be a server solution
My (year old) experience with CouchDB has been that it is a poor database,
especially in what they consider "large" amounts of data. I was working
with a dataset of 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/30/2011 10:45 AM, Alexey Pechnikov wrote:
> Very interesting annonce:
> http://www.couchbase.com/press-releases/unql-query-language
It is rather difficult to work out from the spec pages how it differs from
regular SQL. Personally I think it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2011 02:45 PM, Gabor Cselle wrote:
> (My understanding is that SQLite stores 64-bit, not 32-bit integers).
SQLite actually stores integers using a variable length encoding and is
documented here:
http://www.sqlite.org/fileformat.html#vari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 07:39 PM, Simon Slavin wrote:
> Actually I don't see how BLOBs can be used in an index anyway, since
> technically blobs have no ordering.
memcmp provides an ordering just as it can for strings without a collation.
(That is what SQLite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 03:05 PM, Dale Arntson wrote:
> I installed python 2.7.1 for AIX 6.1 (64 bit), but it appears to be
> missing the _sqlite3.so library, even though this is a standard library
> that comes with the current python release on all other plat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 06:57 PM, Simon Slavin wrote:
> Would it improve the SQLite time if it was changed to strings instead of
> BLOBs ?
Note that internally SQLite treats strings and blobs virtually identically.
Usually the same data structure and function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 09:21 AM, Clifford Hung wrote:
> For statements, sqlite3_next_stmt() can be called to return a pointer to the
> first prepared statement associated with a database connection
In my opinion that API is a huge mistake outside the context
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/28/2011 12:40 AM, Baruch Burstein wrote:
> On the same topic, I know the documentation says SQLITE_OMIT_* are not
> supported by the amalgamation, but I have used many of them to successfully
> reduce my object file. Is there any documentation on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/27/2011 04:16 AM, Baruch Burstein wrote:
> The thing I don't understand is how can this be, because when I search
> sqlite3.c for "SQLITE_OMIT_UTF16", I am told it doesn't exist in this file!
You need a better search tool. Against the 3.7.7.1 a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> after a quick inspection, i can see (i think) that part of the
> configuration and build process is to *create* the sqlite3.c source
> file to be used as part of the compilation, is that correct?
Yes as Pavel mentioned. The single file is known a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/22/2011 02:06 PM, Kent Tenney wrote:
> I make copies periodically, so I have 2 files
> shotwell_2011-07-21.db and shotwell_2011-07-22.db
Shotwell is open source so you could also modify it to meet your needs. You
won't be the first Shotwell use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/18/2011 07:58 AM, abhisek...@gmail.com wrote:
> So I am coding up a cache simulator.
I suggest having a look at cachegrind which does something similar. You
should be able to learn from their data structures. It is also open source
so maybe y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2011 06:29 AM, Simon Slavin wrote:
> Of course my hacked SQLite library
You don't have to hack the SQLite library. Simply create a virtual table
with the table name they expect and filter out rows as appropriate. The
real table can be in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/15/2011 09:01 PM, san long wrote:
> sqlite3 support a trigger on SELECT ? View is a good solution, but I
> want to let different process see different records, like:
> pid A sees rowid 1,2
> pid B sees rowid 1,3
Add a column to the table for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/15/2011 06:19 PM, san long wrote:
> Is there any good solution to satisfy my requirement?
Since you want absolutely nothing to see them, delete them.
Or make triggers to copy data between the real table that contains all the
data and your surro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/13/2011 10:56 AM, Jan Hudec wrote:
> In my experience, the .o files are significantly larger than the resulting
> binary.
The size command will tell you how big the code (aka text), data and zero
initialized data (aka bss) are for object or shar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/13/2011 03:06 PM, Samuel Neff wrote:
> The BerkleyDB backed version of SQLite from Oracle supports page level
> locking. Apparently this is where the real performance gains come from, not
> swapping out the back-end.
That only helps with concur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/2011 08:30 AM, e-mail mgbg25171 wrote:
> I just want to be able to specify different dimensional values and get back
> rectangles of data that I can manipulate.
Is what you are trying to do the same thing as pivot tables in spreadsheets?
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Constlist page:
http://www.sqlite.org/c3ref/constlist.html
The SQLITE_DBSTATUS entries start with what appears to be a title and all
link to a non-existent page.
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/26/2011 03:52 PM, Richard Hipp wrote:
> The bug is that it is returning
> SQLITE_SCHEMA instead of SQLITE_OK. If you wanted to, you could just ignore
> the error and keep going and everything would work.
Will there be a point release soon fixin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/25/2011 01:22 PM, Cheetah wrote:
> What I'm suggesting is that it should be possible to open any file via
> a URI that can be opened using the non-URI open call.
You can. Use this:
file://localhost/\\darkstar\home\fred\data.db
Roger
-BE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2011 08:28 AM, Cheetah wrote:
> The documentation clearly states that using an authority other than
> localhost is not permitted.
This was a deliberate decision when the feature was originally proposed.
The original spec was that the hostname
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/10/2011 12:12 AM, Cecil Westerhof wrote:
> I like to make speed comparisons for sqlite.
Comparing SQLite to other databases? Different versions of SQLite?
Different configurations of the same version of SQLite?
The SQLite source does include a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/09/2011 10:57 AM, Noah Hart wrote:
> there any way to tell which of the constraint would have been violated?
No. Long known issue (since January 2006) with uninformative constraint
failure messages:
http://www.sqlite.org/src/tktview?name=23
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/2011 08:02 PM, prad wrote:
> apsw gives a decent completion but runs into issues with python2:
> see roger binns post 16 aug 03:24 here:
> http://comments.gmane.org/gmane.comp.python.db.sqlite.user/187
> (a solution is provided
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/2011 01:52 PM, Joe Goldthwaite wrote:
> It says the file is schema version 1, user version 2.
That has *nothing* to do with the issue. They are just two fields within a
SQLite 3 database. You can change them to any arbitrary numbers you w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I see you have now taken this up on the python-sqlite mailing list where
we'll deal with the issue. You've seriously mixed up Python, SQLite and
pyqlite issues and Firefox's databases are SQLite 3 so SQLite 2 is
completely irrelevant.
Roger
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/2011 11:41 AM, Joe Goldthwaite wrote:
> The development environment I'm using is locked into
> Python 2.4 and pysql for python 2.4 can only handle the older sqlite format.
I'd suggest getting working with SQLite 3. SQLite 2 is positively anc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/06/2011 04:47 PM, Rense Corten wrote:
> Just to report back on this issue: recompiling as per Nuno's
> instructions indeed solved the problem. Still, if anyone can explain
> to me why the original executable would work without problems on a
> dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/05/2011 12:20 AM, iip wrote:
> As subject, I want to know how search column that contain ascii chr(0), I
> already use google to search but no luck,
>
> I'm using python language.
If you are using APSW then you can define a user defined functio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2011 10:36 AM, Keith Christian wrote:
> What is the procedure to obtain the list archives?
I'd recommend you use Gmane which has messages going back to 2003. They
provide multiple different ways of viewing the messages as well as searching.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2011 02:17 PM, Simon Slavin wrote:
> Do you understand the strange result the OP reported ?
There is no evidence that Python is any way relevant to this issue and the
OP appears to have gone silent. I expect the actual cause is how SQLite w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2011 07:09 PM, Igor Tandetnik wrote:
> For a subselect like the one in question, SQLite picks the value from
> the first row - whichever row this happens to be - and ignores the rest.
> Providing an explicit LIMIT 1, or for that matter LIMIT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2011 12:31 PM, Jay A. Kreibich wrote:
> I suppose it would be technically correct to allow a LIMIT to 0, but
> that seems like a highly questionable approach. Any parameter value
> outside of 0 and 1 *is* non-sense and should be dutiful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2011 01:18 AM, Dagdamor wrote:
> Patrick Earl писал(а) в своём письме Wed, 01 Jun 2011
> 22:24:10 +0600:
>
>> Is there another work-around?
>
> Yes. Do not feed SQLite with stupid queries. ;)
The query was actually correct and not stupid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2011 04:38 AM, Simon Slavin wrote:
> Python is a bytecode language.
That isn't relevant in this case. The code that interfaces Python to SQLite
is written in C. The amount of Python bytecode involved in this benchmark
is irrelevant.
On 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/01/2011 06:42 PM, Patrick Earl wrote:
> So, to move forward on this bug a decision needs to be made at what
> level it will be handled.
>
> 1. At the SQLite level.
That is exactly what the team did. See the timeline:
http://www.sqlite.org/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/01/2011 12:25 PM, Dominique Pellé wrote:
> [Various optimisations]
While those are all valid, they don't address the underlying issue which is
C code taking five times longer than Python code for the same SQLite
operations. In addition that sam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/01/2011 12:25 AM, Alessandro Marzocchi wrote:
> The only thing that this program does
> is creating a database, making a table where a pair of integer maps
> 8192-bytes blobs and writing 100k rows in it. Any suggestions of what
> I could be doin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/31/2011 12:18 PM, Jan Hudec wrote:
> - Is there any way to speed it up?
Another way (somewhat hinted at by Nico) is that you can create these tables
in separate databases and use attach to bring them in. To drop a table you
can just detach an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> It's been that way for 6 years, and nobody has noticed until Patrick
>> complained earlier today.
Schrödinbug - http://en.wikipedia.org/wiki/Unusual_software_bug#Schr.C3.B6dinbug
>> Hence, the fix is a little trickier than it might seem at first g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/31/2011 05:00 AM, Richard Hipp wrote:
> Any parameter that is optimized out
> becomes an anonymous parameter for which sqlite3_bind_parameter_name returns
> NULL.
This is extremely annoying behaviour, unexpected and non-obvious.
The developer w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/31/2011 12:18 PM, Jan Hudec wrote:
> and calculates them again.
Have you considered using virtual tables so that the calculations are done
on access as needed rather than up front?
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/28/2011 09:02 AM, john darnell wrote:
> Is there a function, method or process whereby I can unlock the database when
> it gets locked?
It is locked by another connection or process and you can't ask them to give
up locks using the SQLite API.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/26/2011 10:41 PM, Frank Chang wrote:
>
> Roger Binns, Thank you for your reply.
You never answered the important bit - is your concern about initial
population of the database or about runtime later on.
> Would you expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2011 07:04 PM, Frank Chang wrote:
> While writing the records to to the sqlite database we do a commit every
> 1 records.
>We think we understand that we also need to do a sqlite pragma
wal_checkpoint everytime
>we do a sqlite database c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/23/2011 09:12 PM, John Deal wrote:
> I guess I am lost on how to obtain a many reader or one writer mutex in
> SQLite.
You are confusing locks on the database and locks in the library on a
sqlite3 pointer. The latter is what the mutex alloc fu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/23/2011 08:46 AM, Fabio Spadaro wrote:
> Hi
When you quote other messages, only quote the relevant pieces that you are
replying to. Several hundred lines is not appropriate.
> What is the difference between "sqlite3.version" (typed on command
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2011 07:13 PM, Sam Carleton wrote:
> I have some code that
> responds to SQLITE_BUSY by sleeping for 50 mills and retrying 4 times:
In that case just use the default busy handler. Set a maximum timeout and
it will be used. Behind the scenes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/17/2011 02:22 AM, StyveA wrote:
> I don't understand why when I use the sqlite3_prepare_v2() function, some
> bind_xxx, and then commit, the data stored in my database are redundant..
>
> To be more precise, when I run my code (see below), I obt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 08:49 PM, romtek wrote:
> I don't know about how things work in your world, but in mine requirements
> for apps change sometimes, so I have to enter design stage after an app (may
> be a website) has been released. Perhaps, you are a clai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 07:48 PM, romtek wrote:
> I was describing what I have to do during design time, which often happens
> after a website has been launched and is operational.
Huh? You launch and have a site in production and then you design it?
> I som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 03:05 PM, romtek wrote:
> I want to rename date to dateAdded.
>
> People currently jump through hoops in order to achieve such a simple (from
> the user's point of view) and needed goal:
> http://stackoverflow.com/questions/805363/how-do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 11:14 AM, Steven Parkes wrote:
>> Isn't that exactly what NOMUTEX does?
>
> The docs (http://www.sqlite.org/threadsafe.html) say
>
> The SQLITE_OPEN_NOMUTEX flag causes the database connection to be in the
> multi-thread mode and
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 10:45 AM, Steven Parkes wrote:
> Not trying to throw them away ...
Isn't that exactly what NOMUTEX does?
> trying to switch from Serialized to Multi-thread. My reading of the docs
says that that's what SQLITE_OPEN_NOMUTEX does. Did I mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/2011 09:37 AM, Steven Parkes wrote:
> I've been using sqlite3 under iOS fine in FULLMUTEX mode, but it dies
> horribly with NOMUTEX
What problem are you trying to solve by getting rid of SQLite's mutexes?
Even if you remove them you still h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2011 09:13 PM, Igor Tandetnik wrote:
> prad wrote:
>> i've seen .db and .sqlite and both work.
>> however, is there a rational for one or the other (eg firefox sqlite
>> plugin looks for .sqlite)?
>
> SQLite itself doesn't care. Each applica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2011 09:33 PM, Don Ireland wrote:
> 1) if I were sending from an address other than the subscribed one, I'd get
> those bounce messages telling me that. But I get NO message at all.
> I'll check the message headers over the weekend though.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2011 02:35 PM, Don Ireland wrote:
> Anybody have any ideas? This is really odd.
Two possibilities:
- - You have different from addresses configured on the phone and desktop.
There is no way for the mailing list to know they are the same per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2011 01:26 PM, John Deal wrote:
> Good question. Very possible my understanding is not complete.
This document has the full details:
http://www.sqlite.org/lockingv3.html
>I have basically read and write transactions, each potentially wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/2011 09:38 AM, John Deal wrote:
> I have been working for weeks on this and I feel there must be something
> simple I am overlooking.
Why are you discarding SQLite's builtin and tested mutexes and then
effectively reimplementing your own t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/2011 01:24 PM, Mays, Steve wrote:
> Question 1.) Can "exentension_functions.c" be compiled along with
> "sqlite3.c" into one executable?
>
> Question 2.) If so, how?
>
> Question 3.) If "exentension_functions.c" be compiled into one
> exe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/08/2011 01:46 PM, Simon Slavin wrote:
> Just asking to warn you it's tricky ...
>
> A) When do you consider that a transaction starts ?
> B) How do you deal with ATTACHed databases ?
C) What about SAVEPOINT?
Roger
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/05/2011 04:52 AM, Guillaume BIENKOWSKI wrote:
> Also, I didn't dive in the code, but is there a reason to filter these?
> I guess it is to *not* trigger the callback multiple times (if you do
> multiple calls to step()).
Profile is telling you h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/03/2011 10:25 AM, Dotan Cohen wrote:
> I have seen this issue brought up on all types of software, from Anki
> to Kontact to Yum:
The way this is generally solved is to use a full text search engine. The
various techniques are named things like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2011 10:56 PM, Paul Linehan wrote:
> two days ago - and haven't received a single reply. Is this not the
> correct forum for such a question? Can anybody even see this
> post?
Yes and yes.
http://www.catb.org/~esr/faqs/smart-questions.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/24/2011 02:03 PM, David L wrote:
> This can't be the desired behaviour, can it?
It isn't. The team have fixed the problem:
http://www.sqlite.org/src/timeline
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/21/2011 02:24 PM, Rich Rattanni wrote:
> The result was errno 4, which according to
> my flavor of Linux is EINTR.
I suggest looking into the source 3.7.6 (more recent than your version) and
find EINTR. It looks like your issue is addressed.
R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/20/2011 06:54 AM, thilo wrote:
> They are a great tool ensuring programs have fewer memory leaks, thread
> issues and the like and if one has access to their results, please USE
> it and judge the false positives with human eyes - strcpy & fprint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/18/2011 02:20 AM, Stefan Keller wrote:
> for it kind of weak typing (meaning
> 'weak' compared to the information schema).
SQLite's typing is not weak. YOU GET BACK OUT WHAT YOU PUT IN. I'd argue
other implementations are the problem since the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/17/2011 04:43 PM, Stefan Keller wrote:
> I clearly prefer 'weakly typed' (or even type-less) over "dynamically
> typed" (mentioned in http://www.sqlite.org/datatype3.html ).
The irony is that SQLite is more strongly typed in my opinion. If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/15/2011 06:28 AM, Jaromir Prinzler wrote:
> I use SQLite Amalgamation and compile it with gcc 2.95 under windows xp.
I strongly recommend you get a more recent version of the compiler. MinGW
now has a decent automated installed and you'll get G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/14/2011 07:39 AM, Johannes Radinger wrote:
>> c.execute('SELECT * FROM table ORDER BY X')
>
> Thank you very much, I just found that out myself :)
Incidentally the code above is somewhat brittle. If the database schema
changed at some point in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2011 04:09 PM, Stephan Wehner wrote:
> is there a way to get a pretty-print version of
>
> sqlite> .schema
>
> Would be nice.
The actual table definitions are how you originally supplied them except the
create table words are capitalized.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/2011 08:25 AM, Stephen Blessing wrote:
> It appears that your SQLite3.6.23.1 software may have some security issues
> that need to be addressed:
The tool you used is pathetic. It is about as helpful as saying your house
has "High" security r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/2011 11:16 AM, Sylvain Pointeau wrote:
> I just tried APSW on max os x,
> but how to get the auto-completion to work?
> it does not work for me...
It requires the Python readline module to work as that is what lets you edit
the command line a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/10/2011 07:58 AM, mcnamaragio wrote:
> Could this have caused database corruption?
SQLite does not have ordinary commands that will corrupt the database. How
to corrupt the database is listed in the doc:
http://www.sqlite.org/lockingv3.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/09/2011 02:03 PM, Edzard Pasma wrote:
> I just made an alias in the shell (Unix-) for this tool:
>
> alias apsw='python -c "import apsw;apsw.main()"'
I keep trying to make it so you can do "python -m apsw " and the code is
structured to all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/08/2011 02:40 PM, Edzard Pasma wrote:
> Just found that the APSW shell does tabcomplete (and even for
> tablenames). It is described here:
>
> http://apidoc.apsw.googlecode.com/hg/shell.html
(I'm the APSW author). It also does output colour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/08/2011 12:11 PM, Clemens Eisserer wrote:
> * Which version of the source should I use? The amalgamized source
> isn't really useful, however for all other source-archives its stated
> its not recommended using.
You should check out the code and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/26/2011 03:12 AM, Black, Michael (IS) wrote:
> When you say "All an index does" don't forget that an index is also usually
> smaller than the data, thereby increase cache performance and reducing disk
> seeks.
That is muddied in the case (prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 08:06 PM, Zaryab M. Munir wrote:
> I am consistently observing this error in Linux envrionment.
> Wondering what can be wrong.
By far the best thing to do is use valgrind. You'll immediately see who
allocates and frees memory and when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2011 09:44 AM, Alexander Spence wrote:
> How would I open a database connection using UTF-16 but still be able to
> specify flags. Seems like there would be a sqlite3_open16_v2 but there's not.
Indeed. If you look at the code for sqlite3_o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/08/2011 06:25 AM, Jay A. Kreibich wrote:
> To be more specific, the sqlite_sequence table can be used to find
> the lowest sequence number that *may* be assigned.
In the same situation as OP I wouldn't bother with trying to find out
number
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/07/2011 09:53 PM, RAKESH HEMRAJANI wrote:
> Probleme statement is :
> I want to implement nextval keyword in sqlite
There are two separate issues here. One is wanting to know the next rowid
that will be assigned which you can find using regular
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2011 03:04 PM, Max Vlasov wrote:
> I don't think I need a solution that complex.
You need to be very careful with your terminology :-)
As for getting other data into your database, just do a .dump of a different
SQLite database and run it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
See also http://www.sqlite.org/src/tktview?name=13137dccf3
Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk10DMwACgkQmOOfHg372QQX2QCgoEe5w0hwY8LFEEaN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2011 05:22 AM, Alexey Pechnikov wrote:
> I think one or more hash functions may be
> included into core SQLite.
(Argggh. You posted the same message to multiple mailing lists. That is
annoying.)
Why can't you use the SQLite API in order to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2011 06:31 AM, Max Vlasov wrote:
> For example, currently it's not
> possible for some exotic vfs to selectively import data from a conventional
> format db (CMIIW)
A VFS is only used for reading and writing SQLite's btree pages.
If you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/2011 01:07 AM, Philip Graham Willoughby wrote:
> I argue that this implies a problem in the Chromium sandbox rather than a
> problem in the SQLite code.
SQLite's implementation makes things worse because the xOpen implementation
is not 5 lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2011 01:44 PM, Drake Wilson wrote:
> I'm inclined to believe this nullifies the main argument against
> forking os_unix.c in the absence of strong evidence to the contrary.
Here are some broken things in VFS of varying severity where fixing t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2011 12:41 PM, Drake Wilson wrote:
> Back on the original topic, I would rather think a custom VFS sounds
> like the way to go;
It is technically correct that will work. However it is a *lot* of
maintenance work.
The custom VFS would be a d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/28/2011 11:59 AM, Robert Hairgrove wrote:
> I'm only beginning to delve into the possibilities offered by the VFS
> API in SQLite. However, from what I have seen so far, it seems like a
> very complete abstraction to me.
For one thing a SQLite d
501 - 600 of 1461 matches
Mail list logo
