in reply to Union of 2 hashes don't work.

It's really not easy to see what your code is trying to acheive? Why are you using Tie::ixHash's? Why do you create the hashes in such a long winded way?

The value of $k in the if statement will take two values during the loop: 1 and 2. You then compare these against the constant value $match that has the value 2. So for the first iteration of the while loop you will take the false branch of the loop and the true branch for the second iteration?

It's not clear at all what you mean by "union" of two (or in your case three) hashes? By definition, a hash will only support unique keys. All three of your hashes contain the same keys. If you union these into a single hash, you will end up with the same five keys, the values of which will be the last value assigned to the given key, so the final state of the hash %union will depend upon the order in which the contributing hashes are assigned to it as demonstrated by the code below.

It might be easier in this case if you would describe the application you wish to use this for, in words rather than than code. We might then be able to suggest a better approach to the problem you are trying to solve.

#! perl -slw use strict; use Data::Dumper; use Tie::IxHash; my %login; { tie my %csv, 'Tie::IxHash'; @csv{ qw[one two three four five] } = qw[11 12 13 14 15]; $login{1} = \%csv; } { tie my %csv, 'Tie::IxHash'; @csv{ qw[one two three four five] } = qw[11 12 23 undef 25]; $login{2} = \%csv; } print Dumper \%login; my %union = (%{$login{1}}, %{$login{2}}); print Dumper \%union; my %union = (%{$login{2}}, %{$login{1}}); print Dumper \%union;

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Replies are listed 'Best First'.
Re: Re: Uniion of 2 hashes don't work.
by toadi (Chaplain) on Jan 10, 2003 at 13:20 UTC
    Well I actually did it on a other way...

    - I had 2 queries from a db.
    - I wanted to write the results in a csv(fixed order so tie).
    - But in the first query i had a key login and if this key existed in second query I wanted the data from both queries as a union on one line in the csv.(both had common fields and unique fields to the both queries)

    I solved it on db-level:
    - I made a new table in oracle where i put the data from query one. Then do a insert or update(to login) with second query.(first i did it with tempory tables in memory, but dumped that idea).
    - Finally I read out that table and make the csv.

    This solution is also good for knowing on which day what data should be in that csv. If something went wrong with creating the csv and/or sending it to the outside party. I easily can redo this step, because of this table.


    For the ones who would be interested hacked a small sample, how i could do it on perl-level:
    # record 1 $login = "me"; $name = "toadi"; $email = "toadi@toadi.be"; $contract = "SERVICE"; $csv{$login}{name}=$name; $csv{$login}{email}=$email; $csv{$login}{contract}=$contract; # record 2 $login = "u"; $name = "other one"; $email = "other@other.be"; $contract = "Programming"; $csv{$login}{name}=$name; $csv{$login}{email}=$email; $csv{$login}{contract}=$contract; foreach $login ( keys %csv ) { print "$csv{$login}{name},$csv{$login}{email},$csv{$login}{rek +nr},$csv{$login}{contract}\n"; }
    So if the key exits, it will write over the needed values. If key not exits it wil make a new entry...

    --
    My opinions may have changed,
    but not the fact that I am right