Because Node.js is an extremely fast platform, most of the times developers can't work with slower relative databases like MySQL opting for something much faster like newer and more productive NoSQL databases.
But there are times when developers just can't avoid working with a classic MySQL server, just because of older specs or because of the data's complexity.
In such cases, having something like node-mysql around can be very useful indeed, especially because the module is very easy to config and adapt.
In case this happens to you, there's a lot of node-mysql documentation provided with the package's README file, enough to get any developer acquainted and informed about the module's inner-workings.
What is new in this release:
- Fix Connection.createQuery for no SQL
- Update bignumber.js to 2.0.7
What is new in version 2.7.0:
- Fix Connection.createQuery for no SQL
- Update bignumber.js to 2.0.7
What is new in version 2.6.1:
- Update bignumber.js to 2.0.5.
What is new in version 2.5.5:
- Added code POOL_ENQUEUELIMIT to error reaching queueLimit
- Added enqueue event to pool
- Added enqueue event to protocol and connection
- Blacklist unsupported connection flags
- Make only column names enumerable in RowDataPacket
What is new in version 2.4.3:
- Fix pool.query to use typeCast configuration.
What is new in version 2.4.0:
- Added code POOL_NOEXIST in PoolCluster error
- Added acquireTimeout pool option to specify a timeout for acquiring a connection
- Added connection.escapeId
- Added pool.escapeId
- Added timeout option to all sequences
- Default connectTimeout to 10 seconds
- Fixed domain binding with conn.connect
- Fixed packet.default to actually be a string
- Fixed PARSER_* errors to be catchable
- Fixed PROTOCOL_PACKETS_OUT_OF_ORDER error to be catchable
What is new in version 2.1.1:
- Fixed:
- Specifying values in conn.query({...}).on(...) pattern.
- Long stack trace to include the pool.query(...) call.
What is new in version 2.1.0:
- Added connectTimeout option to specify a timeout for establishing a connection.
- SSL support.
What is new in version 2.0.0-alpha6:
- Added supportBigNumbers option.
- Accept prebuilt Query object in connection.query.
What is new in version v2.0.0-alpha4:
- Fix quick pause() / resume() usage
- Properly parse host denied / similar errors
- Add Connection.ChangeUser functionality
- Make sure changeUser errors are fatal
- Enable formatting nested arrays for bulk inserts
- Add Connection.escape functionality
- Renamed 'close' to 'end' event
- Return parsed object instead of Buffer for GEOMETRY types
- Allow nestTables inline (using a string instead of a boolean)
- Check for ZEROFILL_FLAG and format number accordingly
- Add timezone support (default: local)
- Add custom typeCast functionality
- Export mysql column types
What is new in version v2.0.0-alpha3:
- Treat utf8_bin as a String, not Buffer.
- Handle empty strings in first row column value.
- Honor Connection#nestTables setting for queries.
- Remove CLIENT_INTERACTIVE flag from config.
- Improve docs for connections settings.
- Implement url string support for Connection configs.
What is new in version v2.0.0-alpha2:
- Specify escaping before for NaN / Infinity (they are as unquoted constants).
- Support for unix domain socket connections (use: {socketPath: '...'})
- Fix type casting for NULL values for Date/Number fields
- Add fields argument to query() as well as 'fields' event. This is similar to what was available in 0.9.x.
- Support connecting to the sphinx searchd daemon as well as MariaDB.
- Implement long stack trace support, will be removed / disabled if the node core ever supports it natively.
- Implement nestTables option for queries, allows fetching JOIN result sets with overlapping column names.
- Fix ? placeholder mechanism for values containing '?' characters.
- Detect when connect() is called more than once on a connection and provide the user with a good error message for it.
What is new in version 0.9.6:
- Escape array values so they produce SQL arrays.
- Mention MySQL transaction stop gap solution.
- Mention affectedRows in FAQ.
Requirements:
- Node.js 0.8 or higher
Comentariile nu a fost găsit