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/03/12 11:39:39 UTC
[jira] Created: (TORQUE-1) Equal tablenames in different databases
can lead to errors
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
Assigned to: 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
[jira] Updated: (TORQUE-1) Equal tablenames in different databases
can lead to errors
Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/TORQUE-1?page=all ]
Thomas Fischer updated TORQUE-1:
--------------------------------
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.
This issue corresponds to Scarab issue TRQS285.
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.
> 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 issue corresponds to Scarab issue TRQS285.
--
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
[jira] Updated: (TORQUE-1) Equal tablenames in different databases
can lead to errors
Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (TORQUE-1) Equal tablenames in different databases
can lead to errors
Posted by "Thomas Fischer (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/TORQUE-1?page=all ]
Thomas Fischer updated TORQUE-1:
--------------------------------
Component/s: Village
> Equal tablenames in different databases can lead to errors
> ----------------------------------------------------------
>
> Key: TORQUE-1
> URL: http://issues.apache.org/jira/browse/TORQUE-1
> Project: Torque
> Issue Type: Bug
> Components: Village, Runtime
> Affects Versions: 3.2, 3.1.1, 3.1, 3.0
> Reporter: Thomas Fischer
> Assigned To: 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
[jira] Commented: (TORQUE-1) Equal tablenames in different
databases can lead to errors
Posted by "Thomas Vandahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TORQUE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926738#action_12926738 ]
Thomas Vandahl commented on TORQUE-1:
-------------------------------------
The cache key for this data is built from the jdbc-URL and the table name. So for all URLs carrying the database name this should not be an issue. For all others, this problem remains.
> Equal tablenames in different databases can lead to errors
> ----------------------------------------------------------
>
> Key: TORQUE-1
> URL: https://issues.apache.org/jira/browse/TORQUE-1
> Project: Torque
> Issue Type: Bug
> Components: Runtime, Village
> Affects Versions: 3.0, 3.1, 3.1.1, 3.2
> Reporter: Thomas Fox
> Assignee: Thomas Fox
> Fix For: 4.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
[jira] Resolved: (TORQUE-1) Equal tablenames in different databases
can lead to errors
Posted by "Thomas Vandahl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TORQUE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Vandahl resolved TORQUE-1.
---------------------------------
Resolution: Won't Fix
Fix Version/s: 4.0
Assignee: Thomas Vandahl (was: Thomas Fox)
Village will be removed in Version 4.0 of Torque, so this should be accepted be a permanent restriction of Village.
> Equal tablenames in different databases can lead to errors
> ----------------------------------------------------------
>
> Key: TORQUE-1
> URL: https://issues.apache.org/jira/browse/TORQUE-1
> Project: Torque
> Issue Type: Bug
> Components: Runtime, Village
> Affects Versions: 3.0, 3.1, 3.1.1, 3.2
> Reporter: Thomas Fox
> Assignee: Thomas Vandahl
> Fix For: 4.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org