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

Custom primary key (not keys, just singular) should no longer be a problem for models when using any of the data retrievals with just a number or through associations. Closes #694 #771

Merged
merged 16 commits into from
Aug 9, 2013

Conversation

durango
Copy link
Member

@durango durango commented Jul 16, 2013

Yeah kind of a lot... :P

@leostera
Copy link

👍

@sdepold
Copy link
Member

sdepold commented Aug 4, 2013

can u rebase ?

@sdepold
Copy link
Member

sdepold commented Aug 8, 2013

…dy defined simply callback rather than connecting again).
durango added a commit that referenced this pull request Aug 9, 2013
Custom primary key (not keys, just singular) should no longer be a problem for models when using any of the data retrievals with just a number or through associations. Closes #694
@durango durango merged commit 99d02bd into sequelize:master Aug 9, 2013
@durango durango deleted the association-key branch August 9, 2013 08:30
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 059bab9 on durango:association-key into * on sequelize:master*.

@mickhansen
Copy link
Contributor

What are you doing @coveralls

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.

5 participants