[
https://issues.apache.org/jira/browse/EMPIREDB-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829442#comment-17829442
]
Rainer Döbele commented on EMPIREDB-417:
----------------------------------------
How can one have "{*}multiple constraints on the same column{*}"?
Does this not always result in an empty resultset?
e.g. how can MY_COL='Hello' AND MY_Col='World' ever be true?
Please explain.
> DBCommand Feature Request: add WHERE without overwriting
> --------------------------------------------------------
>
> Key: EMPIREDB-417
> URL: https://issues.apache.org/jira/browse/EMPIREDB-417
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Affects Versions: empire-db-3.1.0
> Reporter: Jan Glaubitz
> Priority: Trivial
>
> DBCommand.where always removes existing DBCompareExpr before adding the new
> one.
> I know this is expected behavior, but this can be annoying when you have to
> add multiple constraints on the same column under coniditions.
> It would be nice to have something like DBCommand.addWhereConstraints but
> without the List.
> Maybe a new where method that has a boolean for overwrite or not?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
