Databases
StackOverflow2013
Postsdbo
POfind extra, missing, invalid strings when comparing two lists in perl
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POfind extra, missing, invalid strings when comparing two lists in perl
    primarykey
    data
    text
    <pre> List-1 List-2 one one two three three three four four five six six seven eight eighttt nine nine </pre> <p>Looking to output</p> <pre> one | one PASS two | * FAIL MISSING three | three PASS * | three FAIL EXTRA four | four PASS five | * FAIL MISSING six | six PASS * | seven FAIL EXTRA eight | eighttt FAIL INVALID nine | nine PASS </pre> <p>Actually the return from my current solution is a reference to the two modified lists and a reference to a "fail" list describing the failure for the index as either "no fail", "missing", "extra", or "invalid" which is also (obviously) fine output.</p> <p>My current solution is:</p> <pre><code>sub compare { local $thisfound = shift; local $thatfound = shift; local @thisorig = @{ $thisfound }; local @thatorig = @{ $thatfound }; local $best = 9999; foreach $n (1..6) { local $diff = 0; local @thisfound = @thisorig; local @thatfound = @thatorig; local @fail = (); for (local $i=0;$i&lt;scalar(@thisfound) || $i&lt;scalar(@thatfound);$i++) { if($thisfound[$i] eq $thatfound[$i]) { $fail[$i] = 'NO_FAIL'; next; } if($n == 1) { # 1 2 3 next unless __compare_missing__(); next unless __compare_extra__(); next unless __compare_invalid__(); } elsif($n == 2) { # 1 3 2 next unless __compare_missing__(); next unless __compare_invalid__(); next unless __compare_extra__(); } elsif($n == 3) { # 2 1 3 next unless __compare_extra__(); next unless __compare_missing__(); next unless __compare_invalid__(); } elsif($n == 4) { # 2 3 1 next unless __compare_extra__(); next unless __compare_invalid__(); next unless __compare_missing__(); } elsif($n == 5) { # 3 1 2 next unless __compare_invalid__(); next unless __compare_missing__(); next unless __compare_extra__(); } elsif($n == 6) { # 3 2 1 next unless __compare_invalid__(); next unless __compare_extra__(); next unless __compare_missing__(); } push @fail,'INVALID'; $diff += 1; } if ($diff&lt;$best) { $best = $diff; @thisbest = @thisfound; @thatbest = @thatfound; @failbest = @fail; } } return (\@thisbest,\@thatbest,\@failbest) } sub __compare_missing__ { my $j; ### Does that command match a later this command? ### ### If so most likely a MISSING command ### for($j=$i+1;$j&lt;scalar(@thisfound);$j++) { if($thisfound[$j] eq $thatfound[$i]) { $diff += $j-$i; for ($i..$j-1) { push(@fail,'MISSING'); } @end = @thatfound[$i..$#thatfound]; @thatfound = @thatfound[0..$i-1]; for ($i..$j-1) { push(@thatfound,'*'); } push(@thatfound,@end); $i=$j-1; last; } } $j == scalar(@thisfound); } sub __compare_extra__ { my $j; ### Does this command match a later that command? ### ### If so, most likely an EXTRA command ### for($j=$i+1;$j&lt;scalar(@thatfound);$j++) { if($thatfound[$j] eq $thisfound[$i]) { $diff += $j-$i; for ($i..$j-1) { push(@fail,'EXTRA'); } @end = @thisfound[$i..$#thisfound]; @thisfound = @thisfound[0..$i-1]; for ($i..$j-1) { push (@thisfound,'*'); } push(@thisfound,@end); $i=$j-1; last; } } $j == scalar(@thatfound); } sub __compare_invalid__ { my $j; ### Do later commands match? ### ### If so most likely an INVALID command ### for($j=$i+1;$j&lt;scalar(@thisfound);$j++) { if($thisfound[$j] eq $thatfound[$j]) { $diff += $j-$i; for ($i..$j-1) { push(@fail,'INVALID'); } $i=$j-1; last; } } $j == scalar(@thisfound); } </code></pre> <p>But this isn't perfect ... who wants to simplify and improve? Specifically ... within a single data set, one order of searching is better for a subset and another order is better for a different subset.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USReed Debaets
    1. USReed Debaets
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POfind extra, missing, invalid strings when comparing two lists in perl
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POfind extra, missing, invalid strings when comparing two lists in perl
      1. This table or related slice is empty.
      1. VTDownMod
    1. COBased on your comments, I think you have some other requirements that you haven't explained. Perhaps you can tell us what you are doing.
      singulars
      1. POfind extra, missing, invalid strings when comparing two lists in perl
      1. USbrian d foy
    2. COThis is an interesting problem, but before I try another answer I want to make sure I'm working on the right problem. In List1, you have a sequence of items. In List2, you expect to see the same sequence (same items in the same order). You want to know when that sequence gets messed up. Besides unexpected items that shouldn't be there, you want to know when something that should be there is missing, when an expected item is repeated, *and*, which you didn't specify, when any expected items show up out of sequence. Is that the problem at hand?
      singulars
      1. POfind extra, missing, invalid strings when comparing two lists in perl
      1. USbrian d foy
    3. COSorry about stepping away last night ... but i ended up implementing levenshtein's distance and then back-traversing the table... I'll post the final solution I may look into transposition as I have already found instances where I would like to identify those scenarios...
      singulars
      1. POfind extra, missing, invalid strings when comparing two lists in perl
      1. USReed Debaets
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload