It's not Ruby that's slow, it's your database

Re:It's not Ruby that's slow, it's your database by JohnBooty on Wednesday November 09, 2022 @01:35AM (#33528156)

    This would make grepping or locating the latest version pretty annoying

Wouldn't this be an issue with any database object managed via migrations? Do any of them make this easy for any database object?

In ActiveRecord, you have your migrations folder(s) and then you have your `structure.sql` (essentially the raw output of mysqldump or pgdump) or the equivalent.

If I need to see the literal database definition of any database object I look it up in there. Not the slickest solution but works well enough - really just a few keystrokes in my editor.

I'd be curious how other migration tools handle (or fail to handle) this.

[ Parent | on HN ]

Re:It's not Ruby that's slow, it's your database by hamandcheese on Wednesday November 09, 2022 @01:18PM (#33535686)

> Wouldn't this be an issue with any database object managed via migrations?

Like I mentioned, check out flyway repeatable migrations.

[ Parent | on HN ]