В сообщении от Monday 21 July 2008 04:59:10 Kang Kai написал(а):
> Thanks for sharing your experience, would you please introduce how you deal
> with the concurrency?
I'm using AOL web server + tclsqlite. Small and fast read/write transactions +
in-memory && file-based database replicas + "db
On Jul 21, 2008, at 5:46 AM, Daniel Önnerby wrote:
> Hi all!
>
> I usually set the sqlite3_busy_timeout to 10 seconds or something like
> that to make sure that my db isn't locked by any other connection
> at the
> same time. This way I usually do not need to check for SQLITE_BUSY.
> Now I
I just tried the same steps on a memorydb using the NOCASE collation
sequence, and it worked fine ...
C:\Src>sqlite3 :memory:
SQLite version 3.6.0
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> .headers on
sqlite> create table foo(myvalue text collate nocase);
On Jul 21, 2008, at 2:10 AM, [EMAIL PROTECTED] wrote:
>
> Hello,
>
> to answer the following question:
>
> Amount of memory for caching one page with x byte page size?
>
> I found in the Draft 3.6.0 Doc the following information:
>
>
> PRAGMA page_size = bytes;
>
> Query or set the page size of
No, assigning collation during index creation makes no difference. I also
tried
REINDEX with no luck.
I am using verison 3.5.9 on a winxp box (forgot to mention that).
csmith
Robert Simpson wrote:
> Does this work?
>
> CREATE UNIQUE INDEX myidx ON test(str COLLATE path);
>
> Robert
>
>
Does this work?
CREATE UNIQUE INDEX myidx ON test(str COLLATE path);
Robert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of C. Smith
Sent: Sunday, July 20, 2008 9:05 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] User-defined collation UNIQUE INDEX
I am trying to add a very simple collation via load_extension. The collation
is
a case-insensitive wchar compare for windows (using _wcsicmp). It is designed
for windows pathnames being stored in utf16. All works fine until I try to add
the final touch, a UNIQUE INDEX.
Question: How do I
The list seems to have mysteriously eaten my attachment (perhaps a bad
configuration setting):
#include
#include
#include
int main()
{
{
sqlite3 *pDatabase;
int iRet = sqlite3_open("foo", );
assert(iRet == SQLITE_OK);
Why does the attached test case show the expected "cannot rollback -
no transaction is active" error with the v1 interface, but the
generic "SQL logic error or missing database" error when using the v2
interface?
If I add a sqlite3_reset to the v2 interface case (treating it like
v1), I get the
"Sherief N. Farouk" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> Does SQLite safely handle concurrent access by multiple processes
> reading/writing from the same db?
Yes. It implements a database-wide multiple-readers-single-writer lock.
> Are there any platform exceptions
> to
Thanks for sharing your experience, would you please introduce how you deal
with the concurrency?
Regards, Kevin.
> Hello!
>
> I did migrate two projects from PostgreSQL (one is ~22 Gb database with very
> complex reports) and now migrate oracle project (>100 Gb billing database
> with
When a process gets SQLITE_BUSY, it needs to wait for the blocking
operation to finish before it can successfully retry (whether it's
just retrying a COMMIT or redoing a whole transaction). How do
people typically handle this?
If a different process is the one holding the lock, then you need
to
"Alexey Pechnikov" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]
> ? ? ?? Sunday 20 July 2008 21:20:19 Jay A. Kreibich
> ???(?):
>> The good news is that you can re-implement the LIKE function fairly
>> easily. There have been a number of posts in the past dealing with
>>
Hi all!
I usually set the sqlite3_busy_timeout to 10 seconds or something like
that to make sure that my db isn't locked by any other connection at the
same time. This way I usually do not need to check for SQLITE_BUSY.
Now I just tried out the sqlite3_enable_shared_cache and has enabled
В сообщении от Sunday 20 July 2008 23:39:34 Alexey Pechnikov написал(а):
> > The good news is that you can re-implement the LIKE function fairly
> > easily. There have been a number of posts in the past dealing with
> > using external Unicode/I18N libraries to implement a more complete
> >
В сообщении от Sunday 20 July 2008 21:20:19 Jay A. Kreibich написал(а):
> The good news is that you can re-implement the LIKE function fairly
> easily. There have been a number of posts in the past dealing with
> using external Unicode/I18N libraries to implement a more complete
> 'LIKE'
Hello,
to answer the following question:
Amount of memory for caching one page with x byte page size?
I found in the Draft 3.6.0 Doc the following information:
PRAGMA page_size = bytes;
Query or set the page size of the database.
The page size may only be set if the database has not yet
On Sun, Jul 20, 2008 at 07:09:54PM +0200, william sqllite scratched on the wall:
> Hi all,
>
> We're trying to get a big dictionary website running on SQLite (was MySQL),
> but we ran into some trouble that we can't really seem to fix.
>
> While we're using UTF-8 coding, a query like
>
>
Hi all,
We're trying to get a big dictionary website running on SQLite (was MySQL),
but we ran into some trouble that we can't really seem to fix.
While we're using UTF-8 coding, a query like
SELECT * FROM language WHERE word like '%o%'
doesn't find words with Ö or ö, while it did in MySQL.
On Sun, 20 Jul 2008 09:03:44 +0200, you wrote:
>Hello to all,
>
>I think I have found a bug in the RTree extension (I'm using version 3.6.0)
>If I run this script :
It works perfectly for me.
Here is my version of the script:
sqlite_version():3.6.0
DROP TABLE IF EXISTS GEO_TEST;
DROP TABLE IF
Hello to all,
I think I have found a bug in the RTree extension (I'm using version 3.6.0)
If I run this script :
DROP TABLE IF EXISTS GEO_TEST;
DROP TABLE IF EXISTS SI_GEO_TEST;
CREATE TABLE GEO_TEST (FID INTEGER PRIMARY KEY NOT NULL, NAME CHAR
NOT NULL, E_UTMX REAL, E_UTMY REAL);
21 matches
Mail list logo
