Luke Stutters

30 minutes is a, that's quite a migration.

30 minutes is a, that's quite a migration.

I'm going to ask the obvious question now, which is, how do you make your system capable of asynchronous table migrations?

I'm going to ask the obvious question now, which is, how do you make your system capable of asynchronous table migrations?

Shout out to Percona guys. I've done some, worked in a place where we had some Percona consultancy. They were really good, really delivered.

Shout out to Percona guys. I've done some, worked in a place where we had some Percona consultancy. They were really good, really delivered.

When are you going to do an episode on that, Dave?

When are you going to do an episode on that, Dave?

I've got a question for you, Kyle. It sounds like you've got a lot of data if you're running 30-minute migrations, and you've got a lot of developers, and you've got good testing, good infrastructure. What I've found is a lot of real...

I've got a question for you, Kyle. It sounds like you've got a lot of data if you're running 30-minute migrations, and you've got a lot of developers, and you've got good testing, good infrastructure. What I've found is a lot of real...

memorable problems i've had is where you get something running and it feels like it's going to be fine but then it gets deployed to the master database and that's the point at which there's some bad data in there there's something in there from ages ago from a previous version and it absolutely sinks you and these days whenever i possibly can i just pull the entire production database out and test against that

memorable problems i've had is where you get something running and it feels like it's going to be fine but then it gets deployed to the master database and that's the point at which there's some bad data in there there's something in there from ages ago from a previous version and it absolutely sinks you and these days whenever i possibly can i just pull the entire production database out and test against that

Do you do that? Or is your database just so huge that you kind of throw it around? You can't do that, especially with a lot of developers.

Do you do that? Or is your database just so huge that you kind of throw it around? You can't do that, especially with a lot of developers.

Yeah, I mean, you must be dealing with a lot of data. And I mean, I've worked with, you call it HIPAA data in the States, where it's kind of confidential data. And that hugely complicates testing data transfers because you have to either heavily anonymize or write your own tools, kind of replicate a few hundred thousand medical records.

Yeah, I mean, you must be dealing with a lot of data. And I mean, I've worked with, you call it HIPAA data in the States, where it's kind of confidential data. And that hugely complicates testing data transfers because you have to either heavily anonymize or write your own tools, kind of replicate a few hundred thousand medical records.

What's wrong with that?

What's wrong with that?

I recently learned how to use the LS command in Pry. And now I just live out of the LS Pry command. The Ruby API traffic's dropped off considerably. I find the dot methods to be quite noisy. This is very verbose if you're kind of trying to pick out which command it is. And I really like the Pry LS command.

I recently learned how to use the LS command in Pry. And now I just live out of the LS Pry command. The Ruby API traffic's dropped off considerably. I find the dot methods to be quite noisy. This is very verbose if you're kind of trying to pick out which command it is. And I really like the Pry LS command.