Re: Comment on module name Data::ETL

ETL::$Brand - That's an excellent idea! -- Robert W. On Wed, May 4, 2016 at 12:15 PM Jed Lund wrote: > I would second the ETL::$Brand suggestion. There isn't necessarily a > consensus on how ETL should be done even outside the perl community. I > also think

Re: Comment on module name Data::ETL

I would second the ETL::$Brand suggestion. There isn't necessarily a consensus on how ETL should be done even outside the perl community. I also think ETL::$Brand honors the perl TIMTOWDI culture and that allows for multiple ETL styles with overlapping function. Jed On Wed, May 4, 2016 at 6:27

Re: Comment on module name Data::ETL

Robert Wohlfarth writes: > I'm weighing 3 ideas... > 2. Create a top-level namespace for ETL. > > Idea 2 looks like so... > * ETL > * ETL::Extract > * ETL::Extract::Excel > * ETL::Extract::DelimitedText > * ETL::Extract::XML > * ETL::Load > * ETL::Load::MSAccess Not necessarily. That would be

Re: Comment on module name Data::ETL

Hi, I noticed that your ETL modules are not designed to use a dimensional model (facts and dimensions), so it may be better to have your own namespace instead of using DataWarehouse namespace. Since it is more generic than a DataWarehouse, I would say Data::ETL is a reasonable option. In fact,

Re: A question of permissions

Hi Buddy, > After I uploaded my new module Date::Easy a while back, I got a failure > notice from PAUSE: I only just noticed your email. PAUSE-related issues are better raised to modu...@perl.org , or you can send to both modules@ and module-authors. >> This