To get source code:
$> git clone git://github.com/Sannis/node-mysql-libmysqlclient.git
$> cd node-mysql-libmysqlclient
If you want to build specific version of node-mysql-libmysqlclient, checkout it:
$> git checkout v1.3.0
To build the binding using node-waf
you should run:
$> make waf
To build the binding using node-gyp
you should run:
$> make gyp
To cleanup:
$> make clean
To run tests:
$> make test
To lint code:
$> # install cpplint.py
$> make lint
The two files required to use these bindings are ./mysql-libmysqlclient.js and ./mysql_bindings.node (build/default/mysql_bindings.node). Put module directory in your NODE_PATH or copy those two files where you need them.
All functions and possible use cases should have tests, places in one of tests
sub-folders.
Also tests/issues
contains tests for some reportes issues and used for regression testing.
node-mysql-libmysqlclient
uses nodeunit
as testing tool. If you contributing something,
you should check that your changes do not breakes tests.
If you chnage small part of code you can test it using:
$> make test
But after all you should run all tests for node-mysql-libmysqlclient
code by executing:
$> make test-all
All branches build status: .
Master
branch build status: .
Go to Travis CI site to view tests results.
Code style based on Node.js code styles.
- Discuss large changes before coding (this is good idea in collaborative development)
- Javascript code should follow Douglas Crockford code conventions for the javascript programming language and be run through Nodelint. And:
- Code should has two space indention
- Multi-line
if
statements must have braces
- C++ code should follow Google's C++ style guide and be run through cpplint.py. And:
- Max line length is 120 symbols
- All code must be MIT licensed
If you have cpplint.py
in $PATH
, you can lint node-mysql-libmysqlclient
code by executing:
$> make lint
I will be happy to hear tips from the more experienced programmers. If you are interested in wide MySQL usage in Node.JS applications, leave your comments to the code. I'll be glad to see your forks and commits in them :)
You can email patches to me or simply fork this repository using GitHub and send a pull request to me.
Thanks!