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

any reason to NOT cache PojoMetadata #81

Closed
dimzon opened this issue Apr 8, 2014 · 5 comments
Closed

any reason to NOT cache PojoMetadata #81

dimzon opened this issue Apr 8, 2014 · 5 comments
Assignees
@aaberg
Labels
feature request priority-low
Milestone
1.5.0

Comments

@dimzon
Copy link
Contributor

dimzon commented Apr 8, 2014

please tell me why is possible to NOT cache it
@aldenquimby
Copy link
Contributor

because we added it a few weeks ago, no other reason. in the past it wasn't cached, and we wanted to allow users to maintain behavior if they needed to for some reason.

@dimzon
Copy link
Contributor Author

dimzon commented Apr 8, 2014

@aldenquimby
"just to get ability" does not answer on "any reason to not cache" question since it doesn't affect any behavior (doesn't have side-effects except perfomance boost) for consumers

@aldenquimby
Copy link
Contributor

i agree we should be able to delete it and always cache

@aaberg
Copy link
Owner

aaberg commented Apr 8, 2014

I agree. No reason to be able to switch it on or off.

@aaberg aaberg self-assigned this Apr 8, 2014
@aaberg aaberg added this to the 1.5.0 milestone Apr 8, 2014
aaberg added a commit that referenced this issue Apr 8, 2014
@aaberg
ref #81 - removed possibility to cache POJO metadata.
d36bda4
aaberg added a commit that referenced this issue Apr 8, 2014
@aaberg
Merge pull request #85 from aaberg/fix-issue-81
06f6106 
ref #81 - removed possibility to cache POJO metadata.
@aaberg
Copy link
Owner

aaberg commented Apr 8, 2014

Fixed

@aaberg aaberg closed this as completed Apr 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aaberg aaberg

Labels
feature request priority-low
Projects
None yet
Milestone
1.5.0
Development

No branches or pull requests
3 participants
@aaberg @dimzon @aldenquimby