NO, This is one of the largest IT (SW development) companies.
Does this matter in anyways?
Regards,
Ravi K
-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2007 8:41 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Journal files not deleted.
--- [EMAIL PROTECTED] wrote:
> It may be more difficult to implement this in a backwards-compatible
> way such that older versions of SQLite can rollback a journal created
> by a newer version if it encounters one.
I wonder if there are many projects that have different versions of
SQLite updatin
--- Dan Kennedy <[EMAIL PROTECTED]> wrote:
> I checked the code and conflict handling mechanisms (OR ERROR,
> OR ABORT, OR REPLACE) do not apply to virtual tables.
...
> Something to think about anyhow... Do we want conflict handling
> for FTS (and other virtual modules)?
It would be nice if any
At 6:45 PM -0700 4/10/07, Darren Duncan wrote:
If one wants to still deny that rolling back a child without rolling
back a parent has no practical use, then we might as well not have
built-in SQL statements that are atomic, because that is exactly the
same end result for users.
If someone is
At 6:05 PM -0600 4/10/07, Dennis Cote wrote:
Darren Duncan wrote:
I think that the question of what would be a reasonable minimum to
do now depends on what SQLite's current behaviour is when an
individual SQL statement fails that is part of a larger transaction.
Of course not. A reasonable mini
But if the option is between implementing nested transactions without binary
journal file compatibility vs not implementing nested transactions at all, I
think the user base at large would benefit most from having the nested
transaction as an option. A warning could be appended to the docs regard
Darren Duncan wrote:
I think that the question of what would be a reasonable minimum to do
now depends on what SQLite's current behaviour is when an individual
SQL statement fails that is part of a larger transaction.
Of course not. A reasonable minimum is to do nothing and leave SQLite as
is
At 9:20 AM -0400 4/10/07, Samuel R. Neff wrote:
Under what circumstances would an older version of SQLite be
used to rollback a newer journal?
Situations I am thinking of include wanting to use multiple
application programs with the same database, and each one includes a
different version of
At 11:46 AM -0600 4/10/07, Dennis Cote wrote:
Samuel R. Neff wrote:
I personally would see value in supporting quasi-nested transactions where
they are nested in name only--increment decrement a counter and commit on
last commit, rollback entire transaction on first rollback. This would have
th
I can imagine that if a descriptor of the BLOB were stored in the
database you could achieve the Oracle case. It would just be a string
of page ids much like a file map in a filing system. The complexity
would be maintaining it during a vacuum and the performance would suffer
from having disk
Hi,
I am running into some issues that seem related to the current database
file size.
Our application is periodically saving about 150MB of data to the
database. Starting around the 30th interval or so, the time to insert
the data grows significantly - it initially goes up by 3-4x but then
ea
Hello Andrew,
Tuesday, April 10, 2007, 3:25:29 PM, you wrote:
AF> Using sqlite3 (3.3.15 or later), is there a method to retrieve portions of a
AF> blob rather than the whole thing?
AF> The equivalent concept in Oracle's programmatic interfaces to C/C++ is by
AF> retrieving a "blob locator" struc
Using sqlite3 (3.3.15 or later), is there a method to retrieve portions of a
blob rather than the whole thing?
The equivalent concept in Oracle's programmatic interfaces to C/C++ is by
retrieving a "blob locator" structure instead of the blob itself, and then
using procedural code to access as mu
You can only open one connection in exclusive mode - even in one process.
-Ursprüngliche Nachricht-
Von: John Stanton [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 10. April 2007 20:14
An: sqlite-users@sqlite.org
Betreff: [sqlite] Exclusive Access
A quick question in case someone has exp
A quick question in case someone has experience before I delve into the
source and write some test programs.
Is there any impediment for two threads to have concurrent read mode
access to a database opened exclusively by a process? Is it feasible
that they use the same database connection or
Samuel R. Neff wrote:
I personally would see value in supporting quasi-nested transactions where
they are nested in name only--increment decrement a counter and commit on
last commit, rollback entire transaction on first rollback. This would have
the advantage that the library would support issu
On 4/10/07, Dan Kennedy <[EMAIL PROTECTED]> wrote:
I checked the code and conflict handling mechanisms (OR ERROR,
OR ABORT, OR REPLACE) do not apply to virtual tables.
Something to think about anyhow... Do we want conflict handling
for FTS (and other virtual modules)?
I think OR REPLACE woul
[EMAIL PROTECTED] wrote:
www.wipro.com
Would this be Wipro, the outsourcing company?
Martin
-
To unsubscribe, send email to [EMAIL PROTECTED]
--
Hi All,
The journal files created during the transactions are not
getting deleted. These files are created per transaction or only one
file per connection? I am seeing hundreds of journal files with a '-'
suffix causing an error "Database disk full" (DB file is stored in flash
card).
Aren't there different levels of backwards compatibility in play here?
Backwards compatibility of the API and making sure begin/commit/rollback
processes work the same with old and new versions is not the same as having
the ability to take a crashed SQLite db including it's rollback journal and
re
I personally would see value in supporting quasi-nested transactions where
they are nested in name only--increment decrement a counter and commit on
last commit, rollback entire transaction on first rollback. This would have
the advantage that the library would support issuing multiple BEGIN
TRANS
A. Pagaltzis wrote:
Hi Jef,
* Jef Driesen [2007-04-06 11:20]:
Q1. Which is more efficient? Two simple queries or one self
join?
I have seen two different types of queries to retrieve a tree.
The first one uses two very simple queries:
SELECT lft, rgt FROM tree WHERE name = @name;
SELECT * FRO
Dennis Cote wrote:
Jef Driesen wrote:
I want to store a tree in an sqlite database. My first choice was the
adjacency list model:
CREATE TABLE tree (
id INTEGER PRIMARY KEY AUTOINCREMENT,
name TEXT,
parent_id INTEGER
);
But this method requires multiple queries to display the entire
With Windows we found a memory leak in Exclusive access mode. Doing just
selects sqlite takes more and more memory. With the same code in Normal access
mode we do not have any memory leaks. Did anyone else find this, too?
We haven't had similar problems with older versions, yet.
Thanks
Juri
On Mon, 2007-04-09 at 13:02 -0700, Scott Hess wrote:
> Thanks for the concise report. I'm going to take a look at this
> today, to see if it's an fts1/2 problem. If it's _not_, I'll still
> look at it, but perhaps with less eventual success :-).
I checked the code and conflict handling mechanism
25 matches
Mail list logo
