Chris Howie

I should note that I run into this behavior when using `new http.Agent({ keepAlive: true })` as well, but not when using `new http.Agent()`. So perhaps this is an issue...

I will try to produce a self-contained repro.

There is still an issue in Node proper, however, as I encounter this error using Node's own http.Agent in keepalive mode.

Personally, I explicitly state the name of the table as a string in the config. ```js const FooTable = dynogels.define('FooTable', { tableName: 'FooTable', // ... }); ``` I found that...

I'm fully on board with that. I think that having dynogels munge the table name in any way violates the principle of least surprise. (To be fair, this functionality was...

The only side effect would be code that depends on the existing structure of errors. For example, in #74 I changed the message from a JSON string to a human-readable...

This is a useful and interesting feature. Bluebird has a similar thing that we use to augment the promise prototype with our own methods, without polluting Bluebird for any other...

As per #123, [the API call being discussed](http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB.html#batchWriteItem-property) allows putting multiple items in a single API call. I believe we can simply reimplement the array case of `model.create()` to use...

@clarkie Are you still wanting help with this? We have quite a few features / fixes that aren't published yet. I haven't heard from you in awhile; if you can...

It looks like this is a conflict between the version of Joi used by dynogels and the version your application is using. @clarkie We should probably make Joi a peer...