Well, the way I would want to see it would require changing some of the
Rhino Etl language, and therefore probably not what a lot of people would
agree to. The suggestion I would have would be to rename "Process" to
"Pipeline", and then use Process to mean the overall ETL process, and
Pipeline would mean the connected operations. So you would see something
like:
[Boo code]
def truncate_table():
...truncate table code
def drop_indexes():
...drop indexes code
operation read_from_csv:
..read from csv code, yield results
process main_process:
truncate_table()
drop_indexes()
pipeline main_pipeline:
read_from_csv()
sqlBulkInsert "name", "table_name"
map "Id", "Id", int
map "somevalue", "somevalue", string
recreate_indexes()
[\Boo code]
You could do this without changing "Process" to "Pipeline" but I think it's
a good idea anyway ;)
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/rhino-tools-dev/-/lRr4HllWEqYJ.
To post to this group, send email to rhino-tools-dev@googlegroups.com.
To unsubscribe from this group, send email to
rhino-tools-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
