boxball VS goqu

I haven't worked with BI tools, but I'll make the same recommendation for Retrosheet data that I always do: check out the Boxball distributions, specifically the CSV files (or the parquet files if you prefer). You can load those right in, rather than futzing with Retrosheet's event files and processing them manually, etc., just to get to the same spot.

The original data source is the Baseball Databank (aka "The Lahman Database"). I use the Boxball distributions, which include both retrosheet and Baseball Databank data.

You know, I thought about that after posting, that the dailies might not be available directly from retrosheet. I use the Boxball distributions, which take the retrosheet data and process it into database images. These distributions include a "daily" table with the daily logs. So apparently Boxball is generating that table.

I used to think the same thing, and then I found the Boxball pre-built images. You still have to be a bit handy to get them working, but it's way easier than starting from scratch with raw retrosheet data. I initially used the postgres image and worked in SQL, and then switched to python/pandas and the parquet files.

I've always been good with data, math, Excel, etc., but decided to take it to another level during the pandemic. The most difficult thing about Retrosheet data is getting into a usable format. Luckily, the boxball project has created a number of ready-to-download images with all of the data, for different database technologies.

For Retrosheet data, I've been using pre-built images from Boxball, rather than going through the whole process of downloading and converting the files from retrosheet. The Boxball images are awesome. I mostly use the Parquet files for Pandas, but they have other formats (e.g., postgres Docker images, CSV, etc) there.

For SQL, I'd probably go with goqu http://doug-martin.github.io/goqu/

I use goqu (https://github.com/doug-martin/goqu)

SQL Builders (think squirrel or goqu)

I've been looking for a package that allows me to build Postgres DDL statements in Golang. I'm currently using Goqu (https://github.com/doug-martin/goqu) for building statements and it works great, however it does not have support for building schemas. Basic things like creating tables, creating indexes. A great one in JavaScript can be found here: (https://knexjs.org/guide/schema-builder.html#essentials) I have been unable to find anything in Go, does anyone know of any packages like this?

Then use something like https://github.com/doug-martin/goqu to build the SQL.

Try this

We've been using goqu and it's super nice! although there are a ton of other query builders that could better fit your use-case.

If the statement is too dynamic to use query parameters I'd ideally use a dynamic query builder rather than concatenating strings. Goqu is a lib like that but I haven't yet used it personally https://github.com/doug-martin/goqu