Dirty Tracking #103

Closed
forker opened this Issue Oct 16, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@forker

forker commented Oct 16, 2013

Hey guys,

I was wondering why dirty tracking is not implemented in activeresource. Is it just a low priority task or vision of gem owners that it shouldn't be there.

I'd like to tackle on this issue anyways, but before I do that I wanted to hear about your position on this.

To outline the Q:
Should dirty tracking be implemented in activeresource ?

@forker

This comment has been minimized.

Show comment Hide comment
@forker

forker Oct 18, 2013

Option 1 (modular) implemented.
Pull request #106

forker commented Oct 18, 2013

Option 1 (modular) implemented.
Pull request #106

@sirwolfgang

This comment has been minimized.

Show comment Hide comment
@sirwolfgang

sirwolfgang May 3, 2014

This seems to me that it should be clearly a thing. RESTful calls are far more costly then DB hits, and we already enjoy using it for those DB hits.

This seems to me that it should be clearly a thing. RESTful calls are far more costly then DB hits, and we already enjoy using it for those DB hits.

@rails-bot rails-bot bot added the stale label May 5, 2017

@rails-bot

This comment has been minimized.

Show comment Hide comment
@rails-bot

rails-bot bot May 5, 2017

This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.

If it is an issue and you can still reproduce this error on the master branch,
please reply with all of the information you have about it in order to keep the issue open.

If it is a pull request and you are still interested on having it merged please make sure it can be merged clearly.

Thank you for all your contributions.

rails-bot bot commented May 5, 2017

This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails team are limited, and so we are asking for your help.

If it is an issue and you can still reproduce this error on the master branch,
please reply with all of the information you have about it in order to keep the issue open.

If it is a pull request and you are still interested on having it merged please make sure it can be merged clearly.

Thank you for all your contributions.

@rafaelfranca

This comment has been minimized.

Show comment Hide comment
@rafaelfranca

rafaelfranca May 5, 2017

Member

This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails team are limited, and so we are asking for your help.

If it is an issue and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If it is a pull request and you are still interested on having it merged please make sure it can be merged clearly.

Thank you for all your contributions.

Member

rafaelfranca commented May 5, 2017

This issue has been automatically marked as stale because it has not been commented on for at least three months.

The resources of the Rails team are limited, and so we are asking for your help.

If it is an issue and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If it is a pull request and you are still interested on having it merged please make sure it can be merged clearly.

Thank you for all your contributions.

@rails-bot rails-bot bot closed this May 13, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment