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 Fischer (JIRA)" <ji...@apache.org> on 2006/05/01 16:54:48 UTC
[jira] Updated: (TORQUE-1) Equal tablenames in different databases
can lead to errors
[ http://issues.apache.org/jira/browse/TORQUE-1?page=all ]
Thomas Fischer updated TORQUE-1:
--------------------------------
Old Scarab Id: TRQS285
Description:
If more than one database is accessed on runtime, and there are tables in different databases which have the same name but a different structure, no datasets can be written to one of the tables.
Reason is that village retrieves information about tables via jdbc, and caches this information. In the cache, the tablename is used as key. Once a table is accessed, the information is cached. If another table with the same name is accessed, wrong information is retrieved from the cache, which leads to errors.
was:
If more than one database is accessed on runtime, and there are tables in different databases which have the same name but a different structure, no datasets can be written to one of the tables.
Reason is that village retrieves information about tables via jdbc, and caches this information. In the cache, the tablename is used as key. Once a table is accessed, the information is cached. If another table with the same name is accessed, wrong information is retrieved from the cache, which leads to errors.
This issue corresponds to Scarab issue TRQS285.
> Equal tablenames in different databases can lead to errors
> ----------------------------------------------------------
>
> Key: TORQUE-1
> URL: http://issues.apache.org/jira/browse/TORQUE-1
> Project: Torque
> Type: Bug
> Components: Runtime
> Versions: 3.2, 3.1.1, 3.1, 3.0
> Reporter: Thomas Fischer
> Assignee: Thomas Fischer
>
> If more than one database is accessed on runtime, and there are tables in different databases which have the same name but a different structure, no datasets can be written to one of the tables.
> Reason is that village retrieves information about tables via jdbc, and caches this information. In the cache, the tablename is used as key. Once a table is accessed, the information is cached. If another table with the same name is accessed, wrong information is retrieved from the cache, which leads to errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org