<div dir="ltr">In the very first DC workshop at NESCent, the final lesson (done by Hilmar) was pipeline that combined data access in SQL with Python analysis (albeit simply calling sqlite and python from bash, not using sqlite from within python). I think this could be a useful end-of-day-2 lesson, particularly if it emphasized workflow reproducibility. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 29, 2015 at 1:29 PM, Ted Hart <span dir="ltr"><<a href="mailto:edmund.m.hart@gmail.com" target="_blank">edmund.m.hart@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Lately I've been doing a lot of database work. One thing I've found is that the provenance of your work flow with databases is much easier to preserve if it's written in R and you interact with the database via RJDBC rather than a stand alone database environment. When I do that I find I have all these adhoc queries that I never remember what order to execute them in. <div><br></div><div>My question is, would this be a worthwhile lesson for DC? Or is it too advanced? Or would efforts be better spent working on the existing curriculum? Or would this make a reasonable addendum to the SQL lesson (it's actually kind of trivial so it might not be worth it's own lesson). </div><div><br></div><div>I welcome some thoughts as I'm happy to take existing code and formalize it into a lesson if the group things it's worthwhile.</div><div><br></div><div>Best,</div><div>Ted</div><div><br></div>
<br>_______________________________________________<br>
dc-discuss mailing list<br>
<a href="mailto:dc-discuss@lists.idyll.org">dc-discuss@lists.idyll.org</a><br>
<a href="http://lists.idyll.org/listinfo/dc-discuss" target="_blank">http://lists.idyll.org/listinfo/dc-discuss</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">~~~~~~~~~~~~~~~~~~~~~~~<br><a href="mailto:karen.cranston@gmail.com" target="_blank">karen.cranston@gmail.com</a><br>@kcranstn<br>~~~~~~~~~~~~~~~~~~~~~~~</div>
</div>