http://dev.helma.org/bugs/show_bug.cgi?id=674 Summary: No need to call containsKey on dirtyNodes before
putting an existing one.
Product: Helma
Version: CVS trunk
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Database Layer
AssignedTo:
helma-dev@...
ReportedBy:
lists@...
Created an attachment (id=116)
--> (
http://dev.helma.org/bugs/attachment.cgi?id=116)
A small optimisation in Transactor#visitDirtyNode
This is a tiny change, but it seems to me that in Transactor#visitDirtyNode it
is slower to check wether dirtyNodes contains a key before setting it, in order
to prevent setting it again.
Why not simply setting it again?
--
Configure bugmail:
http://dev.helma.org/bugs/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Helma-dev mailing list
Helma-dev@...
http://helma.org/mailman/listinfo/helma-dev
