updated package dependencies, implemented "or null" operator for WHERE clauses, added support for auto created/updated timestamp columns #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've updated all the dependencies of FastLegS so that it works correctly with Node 0.6.0+.
I added an "or null" operator for WHERE clauses so you can say things like "value is 0 or null". I think this is a pretty common use case, and it was impossible to express before. Example of how it is used:
This will return all rows where the "indexed_at" column is before
indexTimeor "indexed_at" is NULL.My third change is support for automatically setting created and updated time stamps for each row. You configure them like so:
The column names can be whatever you want, in this example I use the Ruby nomenclature of "updated_at" and "created_at" as the column names. You don't have to specify both created and updated. Every time you issue a create() or update() call, the relevant column will be updated (in the case of create(), update is also set to the same time).