You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2018/10/19 10:49:00 UTC

[jira] [Closed] (EMPIREDB-172) Allow choice of commandParameter usage / preparedStatements with the creation of a DBCommand object

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

Rainer Döbele closed EMPIREDB-172.
----------------------------------
    Resolution: Won't Fix

Not required

> 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 was sent by Atlassian JIRA
(v7.6.3#76005)