http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Well, what would you have instead? This is a ETL project, I don't see any better way to handle this, frankly. http://ayende.com/2649/rhino-etl-full-package-syntax#comment5http://ayende.com/2649/rhino-etl-full-package-syntax#comment5Mon, 23 Jul 2007 20:01:58 GMTLooking good. I'm coming from a non-ORM background, so I have issues with the literal sql strings. Can't you do anything about those? http://ayende.com/2649/rhino-etl-full-package-syntax#comment4http://ayende.com/2649/rhino-etl-full-package-syntax#comment4Mon, 23 Jul 2007 19:55:56 GMTUm. WOW is all I can say. That is very nice short and concise language. I have to admit that I've used C# instead of SSIS in cases where I can get away with it, but for my next case I'll be looking at these bits. http://ayende.com/2649/rhino-etl-full-package-syntax#comment3http://ayende.com/2649/rhino-etl-full-package-syntax#comment3Sun, 22 Jul 2007 16:15:46 GMT> I realise you're doing this to solve your own problems, not mine, I am looking forward to see what you can do with this :-) => is not a valid Boo operator, so I used >>, but other than that, isn't your map basically a transform of column names? transform SkandiaFileFormatToDestinationsTable: Row.customer_id = Row["Customer ID"] I will probably not allow a file include, but rather a project system, which will allow better reuse (including shared dlls). http://ayende.com/2649/rhino-etl-full-package-syntax#comment2http://ayende.com/2649/rhino-etl-full-package-syntax#comment2Sun, 22 Jul 2007 13:38:15 GMTAll looks good to me :) I realise you're doing this to solve your own problems, not mine, but some other thoughts I've had on this are: 1) Mappings It's common to set up a *mapping* for each source, which indicates how source columns map to target columns. Had you considered making this an explicit concept in your DSL? map SkandiaFileFormatToDestinationsTable: 'Customer ID' => 'customer_id' 'Order ID' => 'order_id' 'First Name' => 'forename' pipeline CopyOrders: Sources.SkandiaFile >> Destinations.ValuationsTable using map SkandiaFileFormatToDestinationsTable 2) Back to the idea of having a stock library of standard cleaning functions. You could just allow file include? pipeline ImportOrdersFromPegasus: include "StandardTransforms.boo" Sources.Orders >> ToTitleCase(Colums: ['Title','Forename','Surname']) >> Destinations.Orders with map PegasusOrdersToSunOrders Food for thought, anyway! http://ayende.com/2649/rhino-etl-full-package-syntax#comment1http://ayende.com/2649/rhino-etl-full-package-syntax#comment1Sun, 22 Jul 2007 13:09:08 GMT