db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vandahl (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TORQUE-1) Equal tablenames in different databases can lead to errors
Date Sun, 31 Oct 2010 17:16:24 GMT

    [ 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
> 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

View raw message