You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built node-sqlite3 (in Release) for Windows using the work of TooTallNate here: #61 and verified that the small Ipsum Lorem example in the README.md worked as expected, using node 0.6.10.
Then I tried to node createdb.js. After the usual spike in memory use, I ended up with a big.db of zero bytes and "DOS" ERRORLEVEL equal to 3.
If I reduce the number of rows inserted by createdb.js from 10 million to 1 million, I get a database of size consistent with expectations (about 65MB) for the random strings.
Platform is 32-bit Windows XP.
My typical uses of sqlite are for small test databases, so I have no idea if this is an issue with SQLite on Windows (I know for a fact that this problem does not occur on 64-bit Linux where I have build and tested node-sqlite3 with node0.6.10.) or node or node-sqlite on Windows.
Please let me know how I can provide a more useful report.
The text was updated successfully, but these errors were encountered:
I built node-sqlite3 (in Release) for Windows using the work of TooTallNate here: #61 and verified that the small Ipsum Lorem example in the README.md worked as expected, using node 0.6.10.
Then I tried to node createdb.js. After the usual spike in memory use, I ended up with a big.db of zero bytes and "DOS" ERRORLEVEL equal to 3.
If I reduce the number of rows inserted by createdb.js from 10 million to 1 million, I get a database of size consistent with expectations (about 65MB) for the random strings.
Platform is 32-bit Windows XP.
My typical uses of sqlite are for small test databases, so I have no idea if this is an issue with SQLite on Windows (I know for a fact that this problem does not occur on 64-bit Linux where I have build and tested node-sqlite3 with node0.6.10.) or node or node-sqlite on Windows.
Please let me know how I can provide a more useful report.
The text was updated successfully, but these errors were encountered: