This repository was archived by the owner on Mar 4, 2025. It is now read-only.
Trying to get underscored fields to work #19
Conversation
This file contains hidden or 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
gfzabarino
commented
Nov 11, 2014
gfzabarino
commented
- Upgraded sequelize to 2.0.0-rc2.
- Changed database schema to use the createTable method when possible and changed all camel case names to underscore.
- Changed all models to have the 'field' attribute set to indicate the real name of fields in the database (and still be able to use camel case names on js).
- Added of a function to controllerHelper.js to convert values to its underscored version. This is used by the getAll method, since apparently sequilize is not respecting the field attribute in some cases.
- Changed all enums values to uppercase.
- Explicitely included createdAt and updatedAt attribtues with their own 'field' setting because model tests were not passing.
- Not working because the hasMany association doesn't respect the foreignKey set in the belongsTo side. It currently inserts its own key, such as ChallengeId (this is happening for files).
- Changed database schema to use the createTable method when possible and changed all camel case names to underscore. - Changed all models to have the 'field' attribute set to indicate the real name of fields in the database (and still be able to use camel case names on js). - Added of a function to controllerHelper.js to convert values to its underscored version. This is used by the getAll method, since apparently sequilize is not respecting the field attribute in some cases. - Changed all enums values to uppercase. - Explicitely included createdAt and updatedAt attribtues with their own 'field' setting because model tests were not passing. - Not working because the hasMany association doesn't respect the foreignKey set in the belongsTo side. It currently inserts its own key, such as ChallengeId (this is happening for files).
Contributor
|
@gfzabarino @indytechcook |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.