but I'll say quickly ... the basis for what I'm mentioning is that we have a Relation, which is a role, that can be implemented either in memory or as a tied object with a db backend; but, if you use several together or do multiple actions on one, they can be rearranged into different actions behind the scenes that are more efficient

once this is done ... no more SQL ... you write your queries in natural perl 6, with things that look like standard Perl functions like maps and greps and junctions and sets, as if each database table was an in-memory array or something ... that's my goal

"dduncan" at 24.69.53.198 pasted "crash report for ./pugs t/pugsrun/07-dash-uppercase-v.t ... may be due to memory corruption from local dirty power, though" (70 lines, 3.6K) at http://sial.org/pbot/17950

audreyt: http://sial.org/pbot/17962 ... the interface is the same of Judy.Map (which uses JudyHS), but JHS+Iter still segfaulting. 'make smoke' result for patched took almost the same time. in theory JHS will be better on this. comments?