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.

Sign up for GitHub

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

Jump to bottom

Instance.copy #2486

Open
mickhansen opened this issue Oct 27, 2014 · 18 comments
Open

Instance.copy #2486

mickhansen opened this issue Oct 27, 2014 · 18 comments
Labels
status: understood For issues. Applied when the issue is understood / reproducible. type: feature For issues and PRs. For new features. Never breaking changes.

Comments

@mickhansen
Copy link
Contributor

Instance.copy(ovewrite{}) would create a new instance based on the current instance values overwritten by the passed in values.
@mickhansen mickhansen added the type: feature For issues and PRs. For new features. Never breaking changes. label Oct 27, 2014
@mlegenhausen
Copy link
Contributor

+1 excluding or including attributes would be nice.

@mickhansen
Copy link
Contributor Author

@mlegenhausen yeah i'm thinking we'd still support fields.

@aarosil
Copy link

aarosil commented Jun 30, 2015

+1, any way I can help let me know

@EToreo
Copy link
Contributor

EToreo commented Jan 27, 2016

+1

Should fields marked as auto-increment be forced to null on copy? That seems like the default behavior I would want.

@panbanda

This comment was marked as spam.

Sign in to view
@mickhansen
Copy link
Contributor Author

@EToreo Yeah autoIncrement fields should be removed

@julestruong

This comment was marked as spam.

Sign in to view
3 similar comments
@rfink

This comment was marked as spam.

Sign in to view
@Kevin170113664

This comment was marked as spam.

Sign in to view
@Dezzymei

This comment was marked as spam.

Sign in to view
@felixfbecker
Copy link
Contributor

Please don't +1 issues. It clutters the thread without adding value to the discussion and spams maintainers with notifications. Use GitHub reactions to upvote features.
image

@stale stale bot added the stale label Jun 29, 2017
@stale

This comment was marked as outdated.

Sign in to view
@stale stale bot closed this as completed Jul 6, 2017
@sushantdhiman sushantdhiman reopened this Sep 15, 2017
@stale stale bot removed the stale label Sep 15, 2017
@paulius005
Copy link

bump, because wishful thinking

@aryeharmon
Copy link

bump again, because even more wishful thinking

@stale

This comment has been minimized.

Sign in to view
@stale stale bot added the stale label Jul 23, 2019
@papb papb removed the stale label Jul 24, 2019
@thfrei
Copy link

thfrei commented Aug 12, 2019

It would be nice...

@papb papb added the status: understood For issues. Applied when the issue is understood / reproducible. label Aug 13, 2019
@papb
Copy link
Member

papb commented Aug 13, 2019

If anyone is willing to submit a PR for this, it would be very welcome!

@rdsedmundo
Copy link

Almost 10 years on and I've found myself in the need for this, or a .clone() method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: understood For issues. Applied when the issue is understood / reproducible. type: feature For issues and PRs. For new features. Never breaking changes.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests