max-mapper / max-mapper/node-mdb
Mac build, stdout issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 34
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
brew install mdbtools worked on mavericks, and I can use the cli tools.
At first I thought it was node-mdb, but I keep getting an error ENOENT or 'no output' from the stream with other libraries (nexpect, spawn-to-readstream) as well. I can mdb-export a mdb to csv via command line. I need to chunk through a ~250mb mdb; streams are ideal. Done it with others (xls, csv, etc), but this is a different type of error. I know that the cli works, so I should be getting data on stdout.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the node-mdb interface and the working mdb-export command on a large MDB file. Compare how stdout is handled with the mentioned stream libraries; done means data is emitted without ENOENT or an empty stream while processing the database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100