I knew once upon a time I saw this, but have never been able to relocate it again, so thanks for mentioning it. Now I can finally see what it does! It gets a list of tables from the DB and then calls the set_up_table method from the driver-specific parts of Class::DBI. Browsing the source of these, none of them seem to do much more than make a list of columns and figure out the primary key. They don't setup lazy loading or any foreign keys, but I think I know why. This approach doesn't seem to match the philosophy of Class::DBI -- it wants you to be able to name a foreign key relation however you like, and lazy load columns however you like (and as the all-purpose tool out there, it should). My module has a much lazier usage philosophy. It's willing to reduce your flexibility and give you some (I think) very reasonable defaults in order to get you up and running with the easy stuff in less time.

blokhead