@michaeldrogalis In general the idea is that migrations are schema-only, and that they should be additive. There is a seed-fn parameter that let's you tack in whatever you want as a post-migration function (which does get a connection if I remember right)

so, you would simply set up your system to run the schema migrations, and include your own subsystem for whatever post-processing/seeding you feel is necessary

@tony.kay We have some atypical requirements that require seed data to be transacted only once. I ended up using a transactor function to get the job done. Worked fine. 🙂

Thank you for the reply!

cool

welcome...sorry for the delay

Not at all, thank you 🙂