Re: [sqlite] SQLite bug on AFP?

2008-06-11 Thread BareFeet
Following up: >>> I think the solution might be as simple as compiling with - >>> DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. >>> It enables some Apple-contributed code that does file locking that >>> works on AFP as well as on other network filesystems that the Mac

Re: [sqlite] SQLite bug on AFP?

2008-06-07 Thread D. Richard Hipp
On Jun 7, 2008, at 4:40 PM, Peter K. Stys wrote: > On Thu, Jun 5, 2008 at 2:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > >> >> On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: >> >>> Hey all, >>> >>> We are getting reports that sqlite is not working for users of AFP >>> (Apple Filing

Re: [sqlite] SQLite bug on AFP?

2008-06-07 Thread Peter K. Stys
On Thu, Jun 5, 2008 at 2:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > > On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: > > > Hey all, > > > > We are getting reports that sqlite is not working for users of AFP > > (Apple Filing Protocol) in Bug 417037 [1]. I was wondering if this > >

Re: [sqlite] SQLite bug on AFP?

2008-06-05 Thread D. Richard Hipp
On Jun 5, 2008, at 1:32 PM, Shawn Wilsher wrote: > On Thu, Jun 5, 2008 at 4:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: >> I think the solution might be as simple as compiling with - >> DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. It >> enables some Apple-contributed

Re: [sqlite] SQLite bug on AFP?

2008-06-05 Thread Shawn Wilsher
On Thu, Jun 5, 2008 at 4:04 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote: > I think the solution might be as simple as compiling with - > DSQLITE_ENABLE_LOCKING_STYLE=1. This option only works on a Mac. It > enables some Apple-contributed code that does file locking that works > on AFP as well

Re: [sqlite] SQLite bug on AFP?

2008-06-05 Thread D. Richard Hipp
On Jun 5, 2008, at 12:09 PM, Shawn Wilsher wrote: > Hey all, > > We are getting reports that sqlite is not working for users of AFP > (Apple Filing Protocol) in Bug 417037 [1]. I was wondering if this > was a known issue, and what we could do to help get this resolved. I think the solution