
Mark Berube - 2011-03-21 14:28:07 -
In reply to message 1 from David Hyland
Good idea. I built this class to save time and clean the code needed with a ludicrous amount working with arrays and single tables. I'd have to think about the structure and the best way to include it into the class, but I'm thinking that the best way to handle that would be to add another dim to the array ...the 1st level's keys would then represent which table the next level's data is relevant to... Then you would be able to drop the set_table method entirely from the class.