<?xml version="1.0" encoding="windows-1252"?>
<node id="985814" title="Re: A question of style: Composite keys to multiple values" created="2012-08-06 15:51:26" updated="2012-08-06 15:51:26">
<type id="11">
note</type>
<author id="616540">
moritz</author>
<data>
<field name="doctext">
&lt;blockquote&gt;And... sure. It works. But the whole approach makes me want to disavow it. The right "value" should be a simple list (or sub-hash? seems unnecessary) containing both values. But using a "two strings smacked together" key just seems wrong. I'm just not sure what would ACTUALLY be simpler (for values of 'simpler' approximating "easier for a programmer to understand.")&lt;/blockquote&gt;

&lt;p&gt;Well, an in-memory database would be nicest, if there is an easy way to query it. And to be fast, it would build two indexes, which would either be b-trees or... *drummroll* hash tables.&lt;/p&gt;

&lt;p&gt;But I wouldn't introduce such a big dependency for a relatively trivial feature.&lt;/p&gt;

&lt;p&gt; So in the end I think it boils down to two hashes, which is the most pragmatic solution in Perl space.&lt;/p&gt;

&lt;p&gt;It works, it isn't very complicated, it's easy to udnerstand for the reader -- what more do you want? Unless memory becomes scarce, I'd stay with the current solution.&lt;/p&gt;

&lt;!-- Node text goes above. Div 
tags should contain sig only --&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-616540"&gt;
[http://perl6.org/|Perl 6 - the future is here, just unevenly distributed]
&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
985798</field>
<field name="parent_node">
985798</field>
</data>
</node>
