Hacker News Reader

It seems that migrations with individual row level manipulation would be tragically slow to execute to me? Like, I have a table with a billion rows, and any normal update statement takes up to an hour. I don’t want to think what an update per row would take.

View on HN

Hi, migrations are 1 select statement + `n` insert statement for `n` rows right now.

This might be improved to insert in batches in the future without changing the API.

I imagine a select on 1B rows will be equally problematic :)

But you are right, it’s not something you necessarily have to worry about now. It just means it doesn’t work for our use case.

Just figured I should point it out.

Reply on news.ycombinator.com