Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for custom column mapping #27

Merged
merged 1 commit into from
Feb 21, 2015

Conversation

raymondfeng
Copy link
Contributor

The PR adds the support for mssql column mapping for model properties.

/to @ritch or @bajtos

'type': 'String', 'required': true, 'length': 20,
'mssql': {
'columnName': 'LOCATION_ID', 'dataType': 'nvarchar',
'nullable': 'N'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this style confusing. IMO you should either put all items on a single line, or else put each key/value pair on a new line.

@bajtos
Copy link
Member

bajtos commented Feb 20, 2015

I am not familiar with this code base. A superfluous inspection did not reveal any major issues. My main concern is whether the new tests cover all places you had to change? See also my style-related comments above.

I'll leave the ultimate decision up to you, feel free to ignore my comments and merge the PR as it is now.

@raymondfeng raymondfeng force-pushed the feature/fix-custom-column branch from 460e07e to 407d4e7 Compare February 20, 2015 17:05
@paulomcnally
Copy link

This solved relations?

With not custom column mapping relations don't work.

@raymondfeng raymondfeng force-pushed the feature/fix-custom-column branch from 407d4e7 to 30e5ee1 Compare February 21, 2015 00:12
raymondfeng added a commit that referenced this pull request Feb 21, 2015
@raymondfeng raymondfeng merged commit efd3644 into master Feb 21, 2015
@paulomcnally
Copy link

Please send release to npm. 👍

@raymondfeng raymondfeng deleted the feature/fix-custom-column branch February 21, 2015 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants