I recently had a case where I needed to stack the strings that I did want,
minus those that I didn't. The in() and like() options weren't all that
flexible given their assumption of known strings and I needed to
accommodate near-hits. I found that group_concat() and regexp() work pretty
well
On 2017/04/19 9:12 PM, Stephen Chrzanowski wrote:
I'm attempting to get a report given by TrustWave trimmed down to results
that can be more easily managed. I've taken the results of a report,
cleaned it up with Excel, then used SQLite Expert to import that result
into a database.
Here are
I don't think like works with a subquery as its righthand operand. Or at least
not the way you're expecting it to. It's probably only using the very first
result of the subquery for all the comparisons. If you're looking for an exact
match then what Simon suggested is the way to go. If you're
As I understand it, "IN" presents an exact match, case sensitive
comparison. Using LIKE was thought to get a list of substrings that could
be anywhere in any string found within the Skip field. So if a row in the
Skip field contained "%Apache HTTP%" then I'd like to see, or not see,
depending on
On 19 Apr 2017, at 8:12pm, Stephen Chrzanowski wrote:
> The query I've been messing with is this:
>
> *select distinct ExtIP, IntIP, Service,Remediation from PMEScan where
> Remediation not like (select distinct Skip from SkipRemed) order by
> upper(Desc),upper(Service)*
I'm attempting to get a report given by TrustWave trimmed down to results
that can be more easily managed. I've taken the results of a report,
cleaned it up with Excel, then used SQLite Expert to import that result
into a database.
Here are the two table DDLs:
CREATE TABLE [SkipRemed] (
6 matches
Mail list logo