You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Thomas Vandahl (JIRA)" <ji...@apache.org> on 2016/09/10 11:05:20 UTC
[jira] [Commented] (TORQUE-347) Reduce the amount of
synchronization in collections used by Torque
[ https://issues.apache.org/jira/browse/TORQUE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479624#comment-15479624 ]
Thomas Vandahl commented on TORQUE-347:
---------------------------------------
[~tfischer]: Why are ColumnMap.inheritanceMaps, DatabaseMap.tables and TableMap.columns synchronized and how are they actually used in the runtime? I see no real reason to keep the XML order outside the generator scope. Am I mistaken?
> Reduce the amount of synchronization in collections used by Torque
> ------------------------------------------------------------------
>
> Key: TORQUE-347
> URL: https://issues.apache.org/jira/browse/TORQUE-347
> Project: Torque
> Issue Type: Improvement
> Components: Runtime
> Affects Versions: 4.0
> Reporter: Thomas Vandahl
> Assignee: Thomas Vandahl
> Fix For: 4.1
>
>
> Torque makes use of Collections.synchronizedMap() in several places where ConcurrentMaps should be used.
> Namely:
> * TorqueInstance.databases
> * (TorqueInstance.managers)
> * ColumnMap.inheritanceMaps
> * ColumnMap.optionsMap
> * DatabaseMap.tables
> * DatabaseMap.optionsMap
> * TableMap.columns
> * TableMap.optionsMap
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org