Re: [sqlite] File locking additions

"mohsen ahmadian" <[EMAIL PROTECTED]> wrote: > hello All > the sqlite cant lock db for security data base if i have a DB and must be > close from Other program and cant Open this DB ,this DBMS not protect DB by > User name and password > i think a sqlite must be have > Mohsen Ahmadian h

Re: [sqlite] File locking additions

You have discovered sqLITE. For the features you need, go to an sqlHEAVY such as Oracle, DB2 or PostgreSQL. mohsen ahmadian wrote: hello All the sqlite cant lock db for security data base if i have a DB and must be close from Other program and cant Open this DB ,this DBMS not protect DB by U

Re: [sqlite] File locking additions

hello All the sqlite cant lock db for security data base if i have a DB and must be close from Other program and cant Open this DB ,this DBMS not protect DB by User name and password i think a sqlite must be have Mohsen Ahmadian

RE: [sqlite] File locking additions

Hi, > I definitely like all the things you've proposed. We currently use > SQLite over NFS (to a NetApp) and while it mostly works, we do > occasionally get locking issues that I'd love to be able to > get rid of. Do you run Solaris or Linux? Cheers, David Carter-Hitchin. -- Royal Bank of

Re: [sqlite] File locking additions

On 7-Mar-06, at 7:06 PM, Adam Swift wrote: In order to provide locking support for database files mounted from remote file systems (NFS, SMB, AFP, etc) as well as provide compatible locking support between database clients both local and remote, I would like to propose some additions to the

Re: [sqlite] File locking additions

[EMAIL PROTECTED] wrote: Helmut Tschemernjak <[EMAIL PROTECTED]> wrote: The current lock offset will not allow to copy open DB files if the database gets larger than 0x4000 bytes. This is because locked regions cannot be copied under Windows, we changed it to: #define PENDING_BYTE

Re: [sqlite] File locking additions

Christian Smith <[EMAIL PROTECTED]> wrote: > > > >3. Extend the sqlite3_open commands to support URI style path > >references in order to specify the file system locking type (as > >opposed to modifying the arguments list). After a little poking > >around on RFC 3986

Re: [sqlite] File locking additions

Helmut Tschemernjak <[EMAIL PROTECTED]> wrote: > The current lock offset will not allow to copy open DB files if the > database gets larger than 0x4000 bytes. This is because locked > regions cannot be copied under Windows, we changed it to: > > #define PENDING_BYTE I64CONST(0x7ff

Re: [sqlite] File locking additions

On Mar 8, 2006, at 8:35 AM, Christian Smith wrote: 1. Support a variety of locking mechanisms, from the lowest granularity (using a .lock file) to the highest (the existing advisory locks). A preliminary list: .lock files, flock, afp locks, posix advisory locks. Why not start with just .

Re: [sqlite] File locking additions

On Mar 8, 2006, at 8:01 AM, Helmut Tschemernjak wrote: Hello Adam, all, Cross platform locking is defiantly very important. The goal should be to use the identical sqlite DB via UNIX, AFP, SMB, NFS and others. My opinion is that it is not needed to have any additional open parameters, ju

Re: [sqlite] File locking additions

On Mar 8, 2006, at 12:27 AM, Manfred Bergmann wrote: Hi. You guys already distribute a SQLite version with locking support for remote databases with Mac OSX. What would be the difference to that mechanism? This would allow for manual configuration of the locking type to be used. Curren

[sqlite] Re: semicolon in string (was Re: [sqlite] File locking additions)

On Thu, Mar 09, 2006 at 10:00:50AM +0200, Roger wrote: > Hello guys. > > I have a small problem.I am trying to write some sql queries. Whenever i > put a semicolon, sqlite returns an error immediately.for instance if i > select as follows > > Select Name||" "||Surname||" ; "||Address as "Details

RE: [sqlite] File locking additions

rg Subject: Re: [sqlite] File locking additions Hello guys. I have a small problem.I am trying to write some sql queries. Whenever i put a semicolon, sqlite returns an error immediately.for instance if i select as follows Select Name||" "||Surname||" ; "||Address as "Details >From Person where PersID=1098

Re: [sqlite] File locking additions

Hello guys. I have a small problem.I am trying to write some sql queries. Whenever i put a semicolon, sqlite returns an error immediately.for instance if i select as follows Select Name||" "||Surname||" ; "||Address as "Details >From Person where PersID=1098

RE: [sqlite] File locking additions

scope. Especially if this would involve custom sync mechanisms designed for each file system. -Original Message- From: Jay Sprenkle [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 8:18 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] File locking additions On 3/7/06, Marian Ol

Re: [sqlite] File locking additions

server for sqlite is not a very complicated task. It can take as few as a couple hours. -Original Message- From: Adam Swift [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2006 6:07 PM To: sqlite-users@sqlite.org Subject: [sqlite] File locking additions All, In order to provide

Re: [sqlite] File locking additions

On Tue, 7 Mar 2006, Adam Swift wrote: >All, > >In order to provide locking support for database files mounted from >remote file systems (NFS, SMB, AFP, etc) as well as provide >compatible locking support between database clients both local and >remote, I would like to propose some additions to the

Re: [sqlite] File locking additions

Hello Adam, all, Cross platform locking is defiantly very important. The goal should be to use the identical sqlite DB via UNIX, AFP, SMB, NFS and others. My opinion is that it is not needed to have any additional open parameters, just use the locking features which are in common between all p

Re: [sqlite] File locking additions

On 3/7/06, Marian Olteanu <[EMAIL PROTECTED]> wrote: > I would say that the best way to access a sqlite database mounted from a > remote file server, concurrently with other processes is through a database > server. My opinion is that the overhead of file sync and file locking for a > remote file s

Re: [sqlite] File locking additions

Hi. You guys already distribute a SQLite version with locking support for remote databases with Mac OSX. What would be the difference to that mechanism? To have this in the original SQLite would be great. Best regards, Manfred Am 08.03.2006 um 11:06 schrieb Adam Swift: All, In order to

Re: [sqlite] File locking additions

In case the designer knows that the DB file will be accessed by a single program-thread throught the run - then there should be some sort of flag indicating that SQLITE should execute minimum locking-related code. We were facing problems with flock over NFS mounted file systems. Since we din't ne

RE: [sqlite] File locking additions

, March 07, 2006 6:07 PM To: sqlite-users@sqlite.org Subject: [sqlite] File locking additions All, In order to provide locking support for database files mounted from remote file systems (NFS, SMB, AFP, etc) as well as provide compatible locking support between database clients both local and

[sqlite] File locking additions

All, In order to provide locking support for database files mounted from remote file systems (NFS, SMB, AFP, etc) as well as provide compatible locking support between database clients both local and remote, I would like to propose some additions to the existing database file locking beha