Spent my whole lunch break fixing a migration that just needed a capital letter changed

I was sitting at my desk at 1pm, halfway through a sad salad, when I noticed my data migration for client accounts kept failing. Checked the logs, traced it back to a mapping file. Turned out I wrote "customer_data" instead of "Customer_Data" in a config file. That was it. 45 minutes of my break gone because of one dumb capital letter. Has anyone else had a similar issue with case sensitivity in migrations?

2 comments

2 Comments

milesp3829d ago

Oh but was it really the capital letter's fault though? Case sensitivity is annoying for sure but configs are usually case sensitive by design so you gotta match exactly what the system expects. In my experience those migration failures usually point to a bigger issue with how you're handling data mapping in the first place. Maybe setting up some kind of validation or auto-matching tool could help you catch stuff like that before it takes down your lunch break lol.

uma_mitchell8329d ago

Got that one time where I had a database connection string that failed cause I used "localhost" instead of "127.0.0.1" and spent an hour googling why my local dev env suddenly stopped working. Turned out my hosts file got messed up in an update.