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

Generated key is too long when a QueryKey from StandardQueryCache is used as key #24

Open
tedeling opened this issue Nov 20, 2015 · 0 comments
Assignees

Comments

@tedeling
Copy link

GeneralDataMemcachedRegion.refineKey does a toString on Hibernate's provided key. This works fine when it's used as 2nd level cache as it's provided a CacheKey object which generates a relatively short toString string.

When used as standard query cache a QueryKey object is provided. The toString of the QueryKey is possibly long as it includes the whole SQL and this is quite often longer than the allowed 250 chars of a Memcached key.

The multitenant issue (#15) is in the same method, will do a PR to fix them both.

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

No branches or pull requests

2 participants