It is certainly a shame, but I'm confident that Dagger and its new DTable should be able to cover all of the ground that JuliaDB covers, while being far easier to maintain. I think JuliaDB had some great ideas, but it didn't go far enough with composability, instead opting to use a limited set of table types (no internal DataFrames.jl support), fully focusing on loading from CSV (which is a horrible data format, albeit very common), and supporting only one CSV reader/writer (CSVFiles.jl). Of course, all of this
could get fixed; but with JuliaComputing no longer funding its direct development, and no one dedicating the large portions of time necessary to fix all the outstanding issues and begin developing and merging features, JuliaDB isn't moving anywhere fast.
Thankfully, Dagger is under active maintenance, and has financial support through the JuliaLab (by employing me). Krystian Guliński, the DTable's author and maintainer, is also interested in developing and maintaining the DTable further (having created it as part of his schooling), and will hopefully stay on the Dagger team for the foreseeable future.
