My thoughts were the following: table name in the statement is ignored, there is only one table per DBM. this allows you to drop in a different DBD later
the column name is ignored, see above For a second run: multiple columns are allowed however, the relationship between the first and second keys MUST be AND. for multi-key systems the data is stored as hash within the DBM value. AND is forced, as an OR makes the initial pass O(n), and that's just silly, there'd be no point in using a DBM for that. -- H4sICNoBwDoAA3NpZwA9jbsNwDAIRHumuC4NklvXTOD0KSJEnwU8fHz4Q8M9i3sGzkS7BBrm OkCTwsycb4S3DloZuMIYeXpLFqw5LaMhXC2ymhreVXNWMw9YGuAYdfmAbwomoPSyFJuFn2x8 Opr8bBBidccAAAA= -- MOTD on Setting Orange, the 7th of Discord, in the YOLD 3168: I'm a message/digest guy in a text/plain world --JP
