I understand that Reactor creates cached query files under 

/reactor/project/projectname/Queries 

 

I have found that for some SELECT queries and some DELETE queries Reactor
attempts to use the same query cache filename for both types of queries.

 

For example, I have found that Reactor uses the same query cache file name
for the following two SQL statements (I have added line breaks for
readability).

 

 

SQL 1

---------

 

SELECT  

[ContactHistoryFiles].[contactHistoryFilesID] AS [contactHistoryFilesID],  

[ContactHistoryFiles].[contactDetailsID] AS [contactDetailsID],  

[ContactHistoryFiles].[salespeopleID] AS [salespeopleID],  

[ContactHistoryFiles].[officeCode] AS [officeCode],  

[ContactHistoryFiles].[directoryPath] AS [directoryPath],  

[ContactHistoryFiles].[filename] AS [filename],  

[ContactHistoryFiles].[originalFileName] AS [originalFileName],  

[ContactHistoryFiles].[dateAdded] AS [dateAdded],  

[ContactHistoryFiles].[addedBy] AS [addedBy],  

[ContactHistoryFiles].[dateUpdated] AS [dateUpdated],  

[ContactHistoryFiles].[updatedBy] AS [updatedBy],  

[ContactHistoryFiles].[fileRenamed] AS [fileRenamed] 

FROM [ContactHistoryFiles] AS [ContactHistoryFiles] 

WHERE [ContactHistoryFiles].[contactDetailsID] = <cfqueryparam
cfsqltype="cf_sql_integer"    value="#arguments.Query.getValue(1)#" />  

 

 

SQL 2

----------

 

DELETE FROM

[ContactHistoryFiles]

WHERE [contactDetailsID] = <cfqueryparam cfsqltype="cf_sql_integer"
value="#arguments.Query.getValue(1)#" />

 

 

 

 

So, if SQL 1 runs first it creates a cache file for the SELECT statement.

 

When I execute SQL 2, it re-runs the cached SELECT statement again rather
than performing a delete.

 

 

 

Anyone encountered this before?



Thanks

 

 

 

 



-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reply via email to