empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] [Assigned] (EMPIREDB-172) Allow choice of commandParameter usage / preparedStatements with the creation of a DBCommand object
Date Mon, 04 Feb 2013 14:20:13 GMT

     [ https://issues.apache.org/jira/browse/EMPIREDB-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rainer Döbele reassigned EMPIREDB-172:
--------------------------------------

    Assignee: Rainer Döbele
    
> Allow choice of commandParameter usage / preparedStatements with the creation of a DBCommand
object
> ---------------------------------------------------------------------------------------------------
>
>                 Key: EMPIREDB-172
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-172
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>            Priority: Minor
>
> Following an initial idea of user Jens it would be useful to choose per Command whether
to use prepared statements or not. Currently this is decided from a property on the database
object.
> But simply adding an additional constructor to DBCommand - as suggested - won't help,
as it is an abstract class and gets instantiated by the driver.
> Some deeper thoughts on this are required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message