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

MR_fetchAllGroupedBy method performs double fetch #432

Closed
wants to merge 1 commit into from
Closed

MR_fetchAllGroupedBy method performs double fetch #432

wants to merge 1 commit into from

Conversation

yvbeek
Copy link

@yvbeek yvbeek commented Mar 19, 2013

The MR_fetchAllGroupedBy method already performs a fetch. The extra fetch command was causing a double fetch.

Issue: #410

The MR_fetchAllGroupedBy method already performs a fetch. The extra fetch command was causing a double fetch.
@tonyarnold
Copy link
Contributor

Hi @Zyphrax — two quick things:

  1. Is there are reason you can't remove the performFetch: in your code? I can see an argument for keeping this in and keeping it simple, but I hesitate to make a change that might break other's use of the method you're modifying;
  2. Can you resubmit this request against the develop branch, please? We avoid committing/merging directly to master;

@tonyarnold tonyarnold closed this Apr 21, 2013
@yvbeek
Copy link
Author

yvbeek commented Apr 21, 2013

@tonyarnold : I've replaced the code in my local solution, but I have to keep in mind to make this change whenever I update my MR pod. I thought the pull request would be usefull because it looks like a bug. I don't see why you would ever want the two fetches to occur directly after one and other, seems like wasting performance. As you can see the code change is minor, to reduce two fetches to one (in line with the other methods).

I don't see how this would break user code. The fetch still happens, only no longer twice in MR code.

I'll have a look if I can make another pull request for the development branch. I'm not that familiar with GitHub yet :)

@tonyarnold
Copy link
Contributor

Hi @Zyphrax — thanks for responding. You're right — I don't know how I didn't see this one the first time around. I'll merge the change in unless you'd like your name to appear in the commit logs. Let me know!

@yvbeek
Copy link
Author

yvbeek commented Apr 21, 2013

Hi @tonyarnold feel free to merge the change. I'm very grateful for this great framework, I was just happy to help.

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.

2 participants