Re: [sqlite] multiuser DB on network share

Oplocks do not break things. Oplocks will guarantee consistency. They are granted when only one client OS has a file open letting that client OS perform locking and caching operations internally without consulting the server each time. If another client wants to open the file, then that second

Re: [sqlite] multiuser DB on network share

-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 >

[sqlite] database image malformed

Using sqlite in our embedded device has offered tremendous capabilities and very conveniently, and I thank the developers and enthusiasts who continue to further this excellent project. I've had one issue that I cannot explain and would ask for some input. sqlite 3.1.3 linux kernel 2.6.12

Re: [sqlite] Shared cache mode issue

On Tue, 2007-01-09 at 08:01 -0800, Peter James wrote: > On 1/9/07, Dan Kennedy <[EMAIL PROTECTED]> wrote: > But it looks to me like commit #3341 (August 2006) covers this > up. #3341 > changes things so that the shared-schema is reset whenever any > connection

Re: [sqlite] multiuser DB on network share

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 it the other day and thought it might be the key to making it work

Re: [sqlite] multiuser DB on network share

I thought I read somewhere in the docs that this was not reliable (maybe I dreamed it)??? This is great if this works, although I might still make the socketserver for notifying when updates has been made. Thank you for your replies. John Stanton wrote: Why not just use the SMB file locks if

Re: [sqlite] multiuser DB on network share

Why not just use the SMB file locks if you are using the SMB networking? Daniel Önnerby wrote: Well.. I do not mean that I will use the socketserver to run queries against it. What I mean is that the database is opened by the applications from a windows share. The socketserver is only used to

[sqlite] Unable to close due to unfinalised statements

i have an fts1 query that if i perform it and then close the database, i get the above error. i looked in and it seems like a query usually calls: vm = compile(sql); ret = _sqlite3_step(vm); i noticed that the pointer to the vm is stored in the db struct as well. in this particular query, the

[sqlite] Any more bugs reports against 3.3.9?

Last call for bug reports against version 3.3.9. Unless something serious comes up, 3.3.10 goes out in the morning. -- D. Richard Hipp <[EMAIL PROTECTED]> - To unsubscribe, send email to [EMAIL PROTECTED]

RE: [sqlite] multiuser DB on network share

Is it server available for the public or everybody has to find its own solution? We need to support access in home networks that usually consist of few PCs. Dusan -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 09, 2007 12:21 PM To:

Re: [sqlite] multiuser DB on network share

That should work quite well. We use such a strategy to implement remote, multi user access to Sqlite databases. the user is unconcerned about locking or contentions. In our case we made the server run on port 80 (HTTP) and use regular HTTP protocol so that it easily penetrates firewalls.

Re: [sqlite] Sqlite design question

Consider having multiple databases. One can have all the read only tables for example and will therefore always be available for reading. Dynamic tables would be in another. You can increase the granularity by having more databases, perhaps as many as one per dynamic table, depending on the

Re: [sqlite] Sqlite design question

On Tue, Jan 09, 2007 at 01:28:21PM +0100, Florian Weimer wrote: > If your database isn't too large, and you aren't running on Windows, > you could make a copy of the database before updating it, so that > readers and the writer work on different databases. I wish ZFS would allow one to

[sqlite] multiuser DB on network share

Hi all! At the company I work we have a windows application that use sqlite for the document format and this works great. We are now thinking about if it would be possible to have multiple users to access the db simultaneously from different computers (like a enterprise edition :) ). I have

[sqlite] Locking support for remote databases with Mac OSX

I think that starting from version 3.3.8 there is the code in os.c that add supports for locking remote databases with Mac OSX. Inside os.c there are a couple of #defines (SQLITE_ENABLE_LOCKING_STYLE, SQLITE_FIXED_LOCKING_STYLE ) that I think should help with my request. My question is:

Re: [sqlite] Sqlite design question

* Ken: > Would the reader be blocked by the writer? Yes. > Would the writer be blocked by the reader? Yes. However, depending on the size of the transactions this may not be an issue. > I guess I'm unclear what I can/cant do using sqlite and how to gain > as much performance as possible.

Re: [sqlite] Single-character pathnames in win2k

>> Can somebody who understands or regularly uses windows please >> look into it for me. > >It seems like changing >nByte = GetFullPathNameW(zWide, 0, 0, ) + 1; >to >nByte = GetFullPathNameW(zWide, 0, 0, ) + 3; >corrects the problem. Not a solution to the problem, but a small optimization

AW: [sqlite] Equivalent of OLE object da

An OLE object is persisted into a stream of bytes. You can store OLE objects into SQLite as a BLOB, but you need to make your own (specialized) implementation of one of the IPersistXXX interfaces (most likely IPersistStream), which stores the object into an SQLite column/reads a serialized object

Re: [sqlite] Shared cache mode issue

On Mon, 2007-01-08 at 16:03 -0800, Peter James wrote: > Hey folks... > > The context of this message is sqlite library version 3.3.6, using the > shared-cache mode, effectively following the test_server.c example. > Immediately upon switching to shared-cache mode we started seeing errors > like

Re: [sqlite] Single-character pathnames in win2k

> Can somebody who understands or regularly uses windows please > look into it for me. It seems like changing nByte = GetFullPathNameW(zWide, 0, 0, ) + 1; to nByte = GetFullPathNameW(zWide, 0, 0, ) + 3; corrects the problem. According to documentation even that + 1 isn't necessary, and