mysql-live-select updated to 0.0.16

* Added instructions to close connections on readme

Author: numtel

.versions

@@ -17,13 +17,13 @@ id-map@1.0.2
 insecure@1.0.2
 jquery@1.11.3
 json@1.0.2
-local-test:numtel:mysql@0.1.2
+local-test:numtel:mysql@0.1.3
 logging@1.0.6
 meteor@1.1.4
 minifiers@1.1.3
 minimongo@1.0.6
 mongo@1.0.11
-numtel:mysql@0.1.2
+numtel:mysql@0.1.3
 observe-sequence@1.0.4
 ordered-dict@1.0.2
 random@1.0.2

README.md

@@ -67,6 +67,21 @@ Name | Listener Arguments | Description
 `removed` | `index, oldRow` | Row removed, after update
 `reset` | `msg` | Subscription reset (most likely due to code-push), before update
 
+## Closing connections between hot code-pushes
+
+With Meteor's hot code-push feature, a new connection the database server is requested with each restart. In order to close old connections, a handler to your application process's `SIGTERM` signal event must be added that calls the `end()` method on each `LiveMysql` instance in your application.
+
+On the server-side of your application, add the event handler like this:
+
+```javascript
+var liveDb = new LiveMysql(Meteor.settings.mysql);
+
+process.on('SIGTERM', function() {
+  liveDb.end();
+  process.exit();
+});
+```
+
 ## Tests / Benchmarks
 
 A MySQL server configured to output the binary log in row mode is required to run the test suite.

package.js

@@ -1,13 +1,13 @@
 Package.describe({
   name: 'numtel:mysql',
   summary: 'MySQL support with Reactive Select Subscriptions',
-  version: '0.1.2',
+  version: '0.1.3',
   git: 'https://github.com/numtel/meteor-mysql.git'
 });
 
 Npm.depends({
   'mysql': '2.5.4',
-  'mysql-live-select': '0.0.15'
+  'mysql-live-select': '0.0.16'
 });
 
 Package.onUse(function(api) {