[IBATISNET-299] Read/write, nonserializable caching generates a new cache key for each request

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: DataMapper 1.6.2
• Component/s: DataMapper
• Assignee: Unassigned
• Reporter: Steven Cottrell
• Created: 27/Jan/10 04:03
• Updated: 27/Jan/10 20:09

Description

Read/write, nonserializable caching appears not to work because consecutive calls from the same thread to a SELECT statement with such a cache model return different objects.

Inspecting the logs reveals that this is because each request gets a new cache key, even though the SQL is identical.

There is an archived email thread about this issue here: http://www.mail-archive.com/[e-mail]/msg02271.html In that thread, Gilles indicates that he checked in a test and it worked; however that test does not expose the issue because it does not use a read/write, nonserializable cache model.

Steps to reproduce:

1) Set up a SQL Map with a read/write, nonserializable cache model and a SELECT statement that uses it (example below)
2) Write a test that calls the statement twice in a row using one of the ISqlMapper QueryForXYZ() methods
3) Run the test with debug logging enabled. Examine the log and note that both statements result in cahce misses using different cache keys

SQL Map snippets:

<cacheModel id="rw-nonserializable-account-cache" implementation="FIFO" serialize="false" readOnly="false">
<flushInterval hours="24"/>
<flushOnExecute statement="UpdateAccountViaInlineParameters"/>
</cacheModel>
...
<select id="GetRWNSCachedAccountsViaResultMap"
resultMap="account-result"
cacheModel="rw-nonserializable-account-cache" extends="GetCachedAccountsViaResultMap">
</select>