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 "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2012/06/21 16:20:42 UTC
[jira] [Commented] (EMPIREDB-148) how to use DBCommond to create a
prepared sql string
[ https://issues.apache.org/jira/browse/EMPIREDB-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398447#comment-13398447 ]
Francis De Brabandere commented on EMPIREDB-148:
------------------------------------------------
Should we set db.setPreparedStatementsEnabled(true) by default or is this a bad idea?
> how to use DBCommond to create a prepared sql string
> -----------------------------------------------------
>
> Key: EMPIREDB-148
> URL: https://issues.apache.org/jira/browse/EMPIREDB-148
> Project: Empire-DB
> Issue Type: Wish
> Reporter: yan zhang
> Priority: Minor
>
> I am working a new project and looking for lightweight ORM tools. One feature I need is to be able to generate sql string and we have our own layer of running query.
> I come across DBCommand class, and it seems to be able to generate raw sql string. One feature I am looking to is able to generate prepared update/insert statement. the getInsert() only returns a regular sql string.
> Would really appreciate if someone can respond on;
> 1) whether this feature is available?
> 2) if not, if this is in your feature plan?
> 3) if yes, code sample will be very helpful.
> thanks,
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira