I am interested to join in this [EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Sunday, February 10, 2008 10:30 PM
To: sqlite-users@sqlite.org
Subject: sqlite-users Digest, Vol 2, Issue 24
Send sqlite-users mailing list submissions to
sqlite-users@sqlite.org
To subscribe or unsubscribe via the World Wide Web, visit
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sqlite-users digest..."
Today's Topics:
1. Re: looping over a result set in a query (Alexander Batyrshin)
2. Re: Quoting identifier vs literal (was: Version 3.2.2) (Kees Nuyt)
3. Re: May one software write to the SQLite database while a
other read the same SQLite database ? (Dusan Gibarac)
----------------------------------------------------------------------
Message: 1
Date: Sat, 9 Feb 2008 18:12:35 +0100
From: "Alexander Batyrshin" <[EMAIL PROTECTED]>
Subject: Re: [sqlite] looping over a result set in a query
To: [EMAIL PROTECTED], "General Discussion of SQLite Database"
<sqlite-users@sqlite.org>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
> Is it possible to refine/combine the above two sets of queries into one?
Yes. It's possible:
A)
SELECT e.to_node_id AS node_id FROM edge e WHERE
e.from_node_id = $node_id
UNION
SELECT e.from_node_id AS node_id FROM edge e WHERE
e.to_node_id = $node_id
B)
SELECT count(edge_id)
FROM edge
WHERE
edge.to_node_id IN (Query_A)
OR
edge.from_node_id IN (Query_A)
------------------------------
Message: 2
Date: Sat, 09 Feb 2008 19:03:36 +0100
From: Kees Nuyt <[EMAIL PROTECTED]>
Subject: Re: [sqlite] Quoting identifier vs literal (was: Version
3.2.2)
To: General Discussion of SQLite Database <sqlite-users@sqlite.org>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
On Sat, 09 Feb 2008 17:16:57 +0100, you wrote:
>On Sat, 9 Feb 2008 23:51:03 +1100, you wrote:
[..]
>>create table MyTable( MyField );
>>alter table MyTable rename to MyNewTable;
>>select SQL from SQLite_Master;
>>
>>which gives:
>>
>>CREATE TABLE 'MyNewTable'( MyField )
>>
>>SQLite should instead use the quotes (if any) used in the alter table
>>command.
>>
>>Tom
>>BareFeet
>
>Reproduced with v3.5.4. I would say that's a bug. You
>could open a bug ticket for it (after checking the
>most recent version still behaves like that).
No need to file a ticket, it has been repaired today:
http://www.sqlite.org/cvstrac/chngview?cn=4781
--
( Kees Nuyt
)
c[_]
------------------------------
Message: 3
Date: Sun, 10 Feb 2008 07:58:48 -0700
From: "Dusan Gibarac" <[EMAIL PROTECTED]>
Subject: Re: [sqlite] May one software write to the SQLite database
while a other read the same SQLite database ?
To: <sqlite-users@sqlite.org>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
We are usually in situation that two processes requiring database access
work at the same time. Any of them can impose implicit lock updating
database. Does it mean that in such scenario we must use
sqlite3_busy_timeout() in front of each database access call to manage a
better way concurrent work?
Dusan Gibarac
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 23, 2008 9:45 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] May one software write to the SQLite database while a
other read the same SQLite database ?
Pierre8r <[EMAIL PROTECTED]> wrote:
> Hello,
>
> One SQLite database on my PC.
> Two softwares.
> May one software write to the SQLite database while a other read the
> same SQLite database ?
>
Your programs cannot be reading and writing at exactly the
same instant in time. But both programs can have the database
open for reading and writing. While one program is writing,
the other is blocked from reading. But the write normally
only takes a few dozen milliseconds. Surely your reader can
wait that long.
The waiting is handled for you automatically if you set
sqlite3_busy_timeout()
--
D. Richard Hipp <[EMAIL PROTECTED]>
----------------------------------------------------------------------------
-
To unsubscribe, send email to [EMAIL PROTECTED]
----------------------------------------------------------------------------
-
------------------------------
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
End of sqlite-users Digest, Vol 2, Issue 24
*******************************************
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
