I decided I’d take a look at Julia again. The SQLite module is very important to me right now. More than important, for me…essential! But I guess I’m too stupid to figure it out. Add to this that some of the documentation applies to different versions. This is something I used early on and got working fairly easily. But it no longer works as it did and the documentation is crap…IMHO. I don’t want to learn the internals of SQLite and/or Julia to tackle a problem. I just want a straight forward way to use SQLite!
Is the problem that in an effort to make the SQLite module do everything there are 10 things you must do before a query (which itself has 50 options/switches) and 10 things after the query. I know I’m not the only one. I read somewhere I’m trying to figure out how to [bla bla bla] using SQLite.jl, but can’t wrap my head around the docs?
To be fair it’s probably or mainly the library and not Julia itself. It’s almost as if it was a personal project that was kindly shared but no effort was given to backward compatibility. If you understand it great if not too bad. There were a few early changes that I adapted to but I don’t want to change my program every time the library changes. I put some programs on github that no longer work. And I’m talking a few month ago not years ago.
What does this example even mean?
DBInterface.execute(db, select) |> DataFrame
Specifically “|> DataFrame”. Is that line a Julia instruction? Is it a julia-ism that I don’t understand at this time. Is it two things? An instruction piped to a DataFrame? If so, the documentation should show it as two steps and leave it to the programmer’s ability to combine them. Don’t show off in documentation. Examples shouldn’t be obfuscated. Explain to a beginner! Why should I care? Because the module will probably be “improved“ in the next version and work totally different anyway.
If I can easily use SQLite on the command line…and I can. Why is it so hard programmatically in Julia?
I haven’t experienced this in Python.