Notices by Pete Corey (petecorey@mastodon.social)

@katafrakt Yeah, that’s the root of the problem here. It’s just so convenient! I imagine separating schema and data migrations and relying more heavily on feature switches is probably the most robust way to handle these things.

@clacke One of these days… But probably not today.

Hello, Mastodon! #introductions

Because, man, homebrew has been awful.

Am I walking down a road of pain if I try to set up my new Mac without homebrew?

@clacke That's a good point. Dropping down the raw SQL does lock me in to a specific tech unnecessarily. Sticking with schemaless Ecto queries is probably the way to go, I guess!

Using Ecto schemas directly in migrations is a huge mistake. I hate my past self for doing it. Every time you modify a schema, all of your past migrations break.

I've since switched to using schema-less queries in migrations, but I'm starting to be of the mind that migrations should just use raw SQL fragments...

#elixir