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 "Ivan Nemeth (JIRA)" <em...@incubator.apache.org> on 2015/09/11 13:10:45 UTC
[jira] [Created] (EMPIREDB-226) Empire generates incorrect SQL when
DBCommand's where list is empty
Ivan Nemeth created EMPIREDB-226:
------------------------------------
Summary: Empire generates incorrect SQL when DBCommand's where list is empty
Key: EMPIREDB-226
URL: https://issues.apache.org/jira/browse/EMPIREDB-226
Project: Empire-DB
Issue Type: Bug
Reporter: Ivan Nemeth
Priority: Minor
if you add an empty constraint list to DBCommand through addWhereConstraints, the resulting sql will end with an empty WHERE.
Example:
DBCommand cmd = db.createCommand();
cmd.select(TABLE.getColumns());
cmd.addWhereConstraints(new ArrayList());
The generated sql will be something like this:
"SELECT t0.name FROM table t0 WHERE"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)