Today I Learned: Do not use transaction as a sqlite table name

I'm in the process of building a dashboard for myself to easily get an overview of my investments. The has been building slowly due to using multiple brokers, and wanting an easier way of benchmarking.

Anyway, at some point I figured having an sqlite database would make sense instead of having many .csvs with different encodings. It also made sense to me that the main table should be called transaction. However, sqlite just returned a OperationalError. Some quick debugging led me realizing that transaction is a keyword in sqlite.