Zach Musgrave

Just an update: I have a prototype of a fix for this working for the original test repro at 5x the original concurrency load. We'll get it cleaned up, add...

I think the reason testify gets pulled in is because we export a set of acceptance tests for integrators (people building a database backend, like Dolt) can use to verify...

Thank you for bringing this to our attention. We did this analysis for dolt, which depends on go-mysql-server, and found that there was only one test file that had this...

Thanks for the contribution, but I don't think we want to concern the library with display widths, as they are deprecated in the current version of MySQL: https://dev.mysql.com/doc/refman/8.0/en/numeric-type-attributes.html Can you...

I agree this is how MySQL works right now, but it's officially unsupported and will not work in the future. For that reason we are not going to add it...

Thanks for drawing this to our attention. I'm digging in a bit more, and I think there may actually be a bug here. I'll let you know what I find....

OK, on closer inspection, dolt_merge() is definitely not going to handle real concurrency without some work on our end. For now our recommendation is to dolt_merge() with only one thread...

If you're running these merge operations from multiple machines, you'll want to lock the branch being merged using database locks, like this: ```go newTx, _ := db.Beginx() _, err =...

Just rediscovering this. This query shouldn't even pass analysis, because the table schema has two columns with the same name, making it ambiguous. We need to come up with a...

Isn't this fixed by new default behavior that lets you commit conflicts?