iptv-filter VS sqlacodegen

I had subscribed to an IPTV service with SO many channels that loading it was a massive pain, so instead I dipped my feet into python for fun and created a filter service that breaks it into a more manageable list:

https://github.com/cmcconomy/iptv-filter

I since stopped subscribing to IPTV so the project is abandoned, but I have a couple of friends who still use it; I'd probably write it completely differently today - but it's still trucking!

https://github.com/cmcconomy/iptv-filter

- load the tables

this makes it really easy to bootstrap the entire db from a folder of parquet files for testing with sqlite and then makes it easy to move to prod on postgres/sqlserver etc. Before I go to prod i still have to add constraints and keys and indexes but that doesn't take too long. then we can use something like alembic on the big sqlalchemy tables definition file to do db migrations.

it's kind of like this: https://github.com/agronholm/sqlacodegen but solving an inverse problem.

basically it bootstraps the db and schemas and gets me like 95% of the way there. my quality of life is better with it.

`sqlacodegen` (https://github.com/agronholm/sqlacodegen) has helped me in the past, plus the ERD diagram tool in dbeaver (https://dbeaver.com/2022/06/30/two-ways-to-use-erd-in-dbeaver/)

Convert it into a sqlite db and use something like sqlacodegen to generate the needed tables/models?

maybe you want to use sqlacodegen to create the classes or tables for you?

I've not used this myself, but you could use sqlacodegen to generate your SQLAlchemy models from the existing tables. From there you would update your queries to work with the models. If you go this route, I'm curious to know how sqlacodegen works out, so please follow up.

I'll be using sqlacodegen to initially populate my ORM, but as the live schema changes I need to be able to run a test on my ORM and see where my table objects are no longer up-to-date.