comment on

Maybe a bit late, but one has to sleep sometimes. Here is the Proper Way™, i.e. using a pull-parser to process the huge XML:

#!/usr/bin/perl
use warnings;
use strict;

use XML::LibXML::Reader;

open my $TXT, '<', '1.txt' or die $!;
my %ids;
while (<$TXT>) {
    undef $ids{ (split /,/)[5] };
}
close $TXT;

my $xml = XML::LibXML::Reader->new( location => '1.xml' )
    or die "Cannot open xml\n";

while ($xml->nextElement('ALERT_ID')) {
    $xml->read;             # Go to the text value.
    my $id = $xml->value;

    if (exists $ids{$id}) {
        delete $ids{$id};

    } else {
        warn "Not found in csv: $id\n";
    }
}
print "$_\n" for keys %ids;
[download]

لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

In reply to Re: Seaching for text in string and comparing to xml, if not found print text by choroba
in thread Seaching for text in string and comparing to xml, if not found print text by helpneeded

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks