Re: [sqlite] SQLite 3.6.22 ATTACH no longer works for files outside the current working directory

On 17 Feb 2010, at 3:44pm, D. Richard Hipp wrote: > On Feb 17, 2010, at 6:52 AM, Hick Gunter wrote: > >> Ok I went back to square one and retrieved the amalgamation source >> from the recommended distribution. It is still failing at the >> "reduce" step before the "shift 627", which is

Re: [sqlite] SQLite 3.6.22 ATTACH no longer works for files outside the current working directory

On Feb 17, 2010, at 6:52 AM, Hick Gunter wrote: > Ok I went back to square one and retrieved the amalgamation source > from the recommended distribution. It is still failing at the > "reduce" step before the "shift 627", which is where the > sqlite3Attach() function is called. > > >

Re: [sqlite] SQLite 3.6.22 ATTACH no longer works for files outside the current working directory

On Feb 15, 2010, at 11:36 PM, Hick Gunter wrote: > In SQLite 3.5.9 it used to be possible to write > > sqlite> ATTACH '/some/unix/file/name.db' AS mydb; > > > In SQLite 3.6.22 this results in the error message > > Error: unable to resolve operation I don't think the above is an SQLite error

Re: [sqlite] SQLite 3.6.22 ATTACH no longer works for files outside the current working directory

On Feb 15, 2010, at 11:36 AM, Hick Gunter wrote: > In SQLite 3.5.9 it used to be possible to write > > sqlite> ATTACH '/some/unix/file/name.db' AS mydb; > > > In SQLite 3.6.22 this results in the error message > > Error: unable to resolve operation Works fine when I try it. Are you using the

[sqlite] SQLite 3.6.22 ATTACH no longer works for files outside the current working directory

In SQLite 3.5.9 it used to be possible to write sqlite> ATTACH '/some/unix/file/name.db' AS mydb; In SQLite 3.6.22 this results in the error message Error: unable to resolve operation whereas sqlite> ATTACH /some/unix/file/name.db AS mydb; is a syntax error at '/' The problem seems to be