Hi Juhani I have tried out the build you have linked to. In fact my test scenario does run without a glitch. I hope these changes are really solving the problem and am looking forward to a stable 1.0 release.
Thanks for pointing it out. Regards Moritz On Thu, Jun 10, 2010 at 5:46 AM, Juhani Ränkimies <[email protected]>wrote: > There is a patch for this problem at > > https://issues.apache.org/jira/secure/attachment/12438770/windows_file_fix_2.patch > . > > It requires a patched erlang to work. The erlang patch is in otp dev > ( > http://github.com/erlang/otp/commit/1ac35cc337f3e9bfdd6a0c64cb089a088811feca > ), > but not in release yet, I think. > > You might want to try setup-couchdb-0.11.0.exe from > http://github.com/juranki/couchdb/downloads. It's an experimental > build of otp r13b04 + erlang_file patch + erlang odbc patches for > nvarchar and timestamp + couchdb 0.11 + windows_file_fix_2.patch. > Please keep in mind that the windows_file_fix_2 hasn't been committed > to any branch of couchdb yet (haven't checked lately) and that there's > no guarantee that it'll be the final solution for the problem. > > cheers, > -juhani > > On Tue, Jun 8, 2010 at 11:12 AM, Moritz Post <[email protected]> wrote: > > Hello Couch People > > > > I am having a serious problem with CouchDB under windows. While running a > > serious of integration tests i have come to a scenario which fails under > > Windows. > > > > The Testsystem that fails is Win7 64bit and CouchDB 0.11.0 installed from > > the installer. I have reproduced the problem under two different Win7 > > systems. The problem does not occure on a Mac running CouchDB 0.11.0. > > > > The following scenario leads to a responds 500 on the last delete > statement. > > Its a series of tests steps to test for the creation of documents and the > > functionallity of the view "getDocuments". All other responds code up > until > > the very last are correct. > > > > The DELETE operation of the last statement does delete all the documents > in > > the database but does not drop the database itself. As you can see > though... > > throughout the code DELETE operation did work (Line 5) > > > > 1> [info] [<0.247.0>] 127.0.0.1 - - 'DELETE' /database 404 > > 1> [info] [<0.1294.0>] 127.0.0.1 - - 'PUT' /database 201 > > 1> [info] [<0.1295.0>] 127.0.0.1 - - 'GET' /database/ 200 > > 1> [info] [<0.1295.0>] 127.0.0.1 - - 'PUT' /database/_design/tpas 201 > > 1> [info] [<0.1302.0>] 127.0.0.1 - - 'DELETE' /database 200 > > 1> [info] [<0.1303.0>] 127.0.0.1 - - 'DELETE' /database 404 > > 1> [info] [<0.1304.0>] 127.0.0.1 - - 'PUT' /database 201 > > 1> [info] [<0.1305.0>] 127.0.0.1 - - 'GET' /database/ 200 > > 1> [info] [<0.1305.0>] 127.0.0.1 - - 'PUT' /database/_design/tpas 201 > > 1> [info] [<0.1312.0>] 127.0.0.1 - - 'GET' > > /database/_design/mydesign/_view/getDocuments?limit=1&descending=true 200 > > 1> [info] [<0.1312.0>] 127.0.0.1 - - 'POST' /database/ 201 > > 1> [info] [<0.1314.0>] checkpointing view update at seq 2 for database > > _design/mydesign > > 1> [info] [<0.1312.0>] 127.0.0.1 - - 'GET' > > /database/_design/mydesign/_view/getDocuments?limit=1&descending=true 200 > > 1> [info] [<0.1314.0>] Shutting down view group server, monitored db is > > closing. > > 1> [info] [<0.1313.0>] 127.0.0.1 - - 'DELETE' /database 500 > > > > I hope anybody is able to tell me what i am doing wrong since this is a > > serious show stopper for our product. > > > > Thanks > > Moritz Post > > >
