Does the TLE layer still add value now that dbdev generates migration files?
The user questions the necessity of the TLE layer in the current dbdev workflow, which generates migration files. They highlight issues with standard PostgreSQL tooling that skips extension member objects, causing problems with pg_dump, supabase db diff, and migration squashing. They propose generating plain SQL migrations instead of TLE-wrapped ones to resolve these issues.