On Sat, Aug 11, 2012 at 04:36:26PM +0200, "José Diaz Seng" wrote: > > > I don't know whether a name such as > > > DBIx::Table::DataGenerator would be better? Given that you have a > database > > > handle, I assume it actively loads the data, rather than generating a > file > > > for later loading. Thus, it is arguably a > > > DBIx::Table::DataGeneratorAndLoader, or even > > > DBIx::Table::TestDataGeneratorAndLoader, but that gets rather unwieldy. > > > (OTOH, the ideas might set your thought processes in motion.) If the > > > module is renamed, would you rename the method too? > > > DBIx::Table::TestDataGenerator seems reasonable. Or perhaps > > DBIx::Table::TestDataPopulate. > > Thanks for the suggestions, how about DBIx::Table::AppendTestData or > DBIx::Table::AddTestData?
The main function of the module, the 'clever' part, is the generation of test data that has referential integrity. Inserting the generated data into the table is relatively trivial. The name should focus on the clever bit more than the trivial bit. So DBIx::Table::TestDataGenerator still seems best to me. Tim.
