You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/10/19 13:52:00 UTC
[jira] [Closed] (DBUTILS-142) Why not design a named parameter?
[ https://issues.apache.org/jira/browse/DBUTILS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed DBUTILS-142.
----------------------------------
Resolution: Invalid
Questions regarding support should go to the mailing list. Improvement requests shalled be formed as such.
> Why not design a named parameter?
> ---------------------------------
>
> Key: DBUTILS-142
> URL: https://issues.apache.org/jira/browse/DBUTILS-142
> Project: Commons DbUtils
> Issue Type: Improvement
> Reporter: objectboy
> Priority: Major
>
> *The dbutils' parameters are dizzying*
> such as:
> insert into a (a, b, c, d, f, g, i, e, g, k) values (?,?,?,?,?,?,?,?,?)
> My eyes have been spent.
> It would be a disaster if the table's fields were told too much
>
>
>
> *Why not*
> such as:
> string sql="select * from user where name=:name";
> .......
> runquery.addParameter("name","paul");
> So simple and straightforward
> No problem with the number, but the parameters of many will be a disaster
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)