You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Brent Daniel (JIRA)" <tu...@ws.apache.org> on 2006/10/17 22:06:34 UTC

[jira] Created: (TUSCANY-866) [DAS] Use overqualified update by default

[DAS] Use overqualified update by default
-----------------------------------------

                 Key: TUSCANY-866
                 URL: http://issues.apache.org/jira/browse/TUSCANY-866
             Project: Tuscany
          Issue Type: New Feature
          Components: Java DAS RDB
            Reporter: Brent Daniel


Currently in the DAS we either use a user-defined version column or do not use any concurrency control. We have enough information to build an overqualified update in cases where a version column is not defined. For example, if a field "name" is changed from "Bob" to "John", we would generate a query such as:

UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob'

If the statement does not update any rows in the database, the DAS will throw a concurrency control exception. 

This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so an exception should be thrown in that case indicating that a version column must be defined. 

-- 
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Resolved: (TUSCANY-866) [DAS] Use overqualified update by default

Posted by "Brent Daniel (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-866?page=all ]

Brent Daniel resolved TUSCANY-866.
----------------------------------

    Resolution: Fixed

Fixed in revision 465025

> [DAS] Use overqualified update by default
> -----------------------------------------
>
>                 Key: TUSCANY-866
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-866
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java DAS RDB
>            Reporter: Brent Daniel
>         Assigned To: Brent Daniel
>
> Currently in the DAS we either use a user-defined version column or do not use any concurrency control. We have enough information to build an overqualified update in cases where a version column is not defined. For example, if a field "name" is changed from "Bob" to "John", we would generate a query such as:
> UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob'
> If the statement does not update any rows in the database, the DAS will throw a concurrency control exception. 
> This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so an exception should be thrown in that case indicating that a version column must be defined. 

-- 
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Assigned: (TUSCANY-866) [DAS] Use overqualified update by default

Posted by "Brent Daniel (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-866?page=all ]

Brent Daniel reassigned TUSCANY-866:
------------------------------------

    Assignee: Brent Daniel

> [DAS] Use overqualified update by default
> -----------------------------------------
>
>                 Key: TUSCANY-866
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-866
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java DAS RDB
>            Reporter: Brent Daniel
>         Assigned To: Brent Daniel
>
> Currently in the DAS we either use a user-defined version column or do not use any concurrency control. We have enough information to build an overqualified update in cases where a version column is not defined. For example, if a field "name" is changed from "Bob" to "John", we would generate a query such as:
> UPDATE CUSTOMER SET NAME = 'John' WHERE ID = 1 AND NAME = 'Bob'
> If the statement does not update any rows in the database, the DAS will throw a concurrency control exception. 
> This scheme will not work in case of LONG VARCHAR, BLOB, or CLOB columns, so an exception should be thrown in that case indicating that a version column must be defined. 

-- 
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org