This content has been marked as final.
Show 5 replies
-
1. Re: performance issue with JDBCCacheLoader
manik Jul 31, 2007 6:12 AM (in response to gmeroz)A find() will load the Pojo, potentially from the cache loader. Nodes are stored in the DB (when using the jdbc cache loader) as blobs, so that blob lookup is necessary to recreate the node in the cache, and then the Pojo before returning the Pojo when calling find().
Perhaps what you need is something like pojoExists() - which may perform a number of cache.hasChild() calls (which in turn calls a number of loader.exists() calls) on the components that make up the Pojo? -
2. Re: performance issue with JDBCCacheLoader
gmeroz Jul 31, 2007 7:40 AM (in response to gmeroz)yes, that's exactly what i'm looking for.
It may perform queries to DB as long as it does not access the Blob column. (like select count(*)...). -
3. Re: performance issue with JDBCCacheLoader
manik Jul 31, 2007 8:55 AM (in response to gmeroz)Why don't you create a JIRA for this as a feature request for the PojoCache API?
-
5. Re: performance issue with JDBCCacheLoader
jason.greene Jul 31, 2007 10:11 AM (in response to gmeroz)As a workaround, you can use:
Fqn fqn = Fqn.fromString("/path/to/pojo"); pojoCache.getCache().getRoot().getChild(fqn.getParent()).getChildrenNames().contains(fqn.getLastElementAsString());