A FQN row of JDBCCacheLoader?

[scotthkao]

Let's suppose there exist the following nodes:
/a/b/c1
/a/b/c2
/a/b/c3

How many rows are there in the jdbc table?
1. only one containing a big "/a" or
2. three rows, each containing /a/b/c1, /a/b/c2, /a/b/c3?

One more question:
If I read attribute "attr1" from /a/b/c1 in the cache, how many rows will be read from jdbc?
1. only "/a" or
2. only /a/b/c1 or
3. all three /a/b/c1, /a/b/c2, /a/b/c3?

Thanks in advance,
Scott

[mircea.markus]

How many rows are there in the jdbc table?

There will be /a, /a/b, /a/b/c1, /a/b/c2 and /a/b/c3

If I read attribute "attr1" from /a/b/c1 in the cache, how many rows
will be read from jdbc?

CacheLoader will load /a, /a/b and /a/b/c1. /a/b/c2 and /a/b/c3 won't be read.

[scotthkao]

Thanks for your answers!

So, if I read attribute "attrB" from the node /a/b, nodes accessed from JDBC will be:
only the two node /a, /a/b and the traversal will stop here without going any further to /a/b/c.
Am I right on this one?

Scott

[mircea.markus]

yes, you are right.