Allows us to define our own timestamp columns. #856
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit allows the user to predefine their own timestamp columns which is useful for databases that already exist. This also allows the user to have their own naming conventions for the timestamp columns. The following options have been added when defining a new table: * createdAt (defaults to "createdAt") * updatedAt (defaults to "updatedAt") * deletedAt (defaults to "deletedAt") * touchedAt (defaults to "touchedAt") Note: The underscored option still remains useful since it's just a simple one line option which allows flexibility for those rare cases in which people decide to change the structure of their database from camelCase to under_score or vice-versa.
|
If this gets pulled we should add an issue to sequelize-doc for these changes :) |
|
what the hell is touchedAt ? |
|
could you add another test for updatedAt ? |
https://github.com/sequelize/sequelize/pull/856/files#L1L376 No idea but it's right there... updatedAt is included in both tests... https://github.com/sequelize/sequelize/pull/856/files#L2R111 |
sdepold
added a commit
that referenced
this pull request
Aug 26, 2013
Allows us to define our own timestamp columns.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit allows the user to predefine their own timestamp columns which is
useful for databases that already exist. This also allows the user to have their
own naming conventions for the timestamp columns.
The following options have been added when defining a new table:
Note: The underscored option still remains useful since it's just a simple one
line option which allows flexibility for those rare cases in which people decide
to change the structure of their database from camelCase to under_score or
vice-versa.