[jira] [Resolved] (EMPIREDB-226) Empire generates incorrect SQL when DBCommand's where list is empty

["Rainer Döbele (JIRA)" <em...@incubator.apache.org>]

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

Rainer Döbele resolved EMPIREDB-226.
------------------------------------
    Resolution: Fixed
      Assignee: Rainer Döbele

fixed as suggested.
Thanks Ivan.

> 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
>            Assignee: Rainer Döbele
>            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)