I’m evaluating SQLDelight, and I’m currently looking into migrations. At first glance, they seem elegantly simple–just drop in an appropriately named file containing your migration and SQLDelight will automatically pick it up, apply it, and validate the resulting schema. Great!
My question is what happens when SQL alone is insufficient to define a migration, such as when a non-trivial data transformation exists between the two schema versions? Other platforms provide a way to interleave migrations written solely in SQL with those written in code. I couldn’t find a similar facility in SQLDelight. Am I missing it, or is some support for this planned?vidmate mobdro word counter