Jeremy Daly

NULL is a valid type, but it doesn't make a lot of sense in NoSQL especially if you have a schema defined via the library. I ran a twitter poll...

Hi @afgallo, The library is still missing Transaction support and a few other small convenience features like GSI Projection Management. Plus there are still a few bugs that people have...

Hey @deldrid1, A lot of work is being done on this and we should see Transactions and TypeScript within the next two weeks. - Jeremy

I've been working on it @deldrid1. The TypeScript conversion has been more difficult than I thought including some refactoring. Hoping to finish it up this week. I'll have to get...

I was playing around with the NoSQL Workbench for Amazon DynamoDB, and looked at the "facets" feature. This gives you a way (when modeling the data) to assign aliases and...

I was thinking this would define them at the `Table` level that would then be mapped to `Model`s (see #15 for my current thinking on this). `Model`s might be too...

Unix timestamps are definitely out. IMO, they don't make sense in a NoSQL DB. AFAIK, there is no difference performance-wise with a string versus a number in DynamoDB. There would...

Hi @rbethel, thanks for the feedback! I actually was thinking about removing `alias` since the `map` functionality makes it redundant. It was a feature in v0.1 (`map` didn't exist), so...

Hi Ryan, There are a few different ways to handle what you're looking for. You can certainly use the custom default functions to construct keys, and it is possible to...

Hi @rbethel, Right now the composite key array mapping only works for one field. You can use the `convert` setting to generate the value that can include other items. Interesting...