Allow DriverSpecificSchemaTestBase::testChangePrimaryKeyToSerial to execute for non-core drivers

Patch

Seems like a simple change.

If this is in DriverSpecificSchemaTestBase can't contrib drivers override the method? Not sure about having core use the less-specific assertion for drivers that pass with the more specific one.

That I can not answer so moving to PNMI per #3

#4 we may, but here I don't think it's relevant the actual value, so by loosening the test we can exatcly avoid contrib to have to override.

Rather, we could write a separate test (this one really driver specific) with different cases of inserting or not a value in a serial column, forcing a gap skip in the autonumbering etc - but that would be a separate issue.

Thanks for answering @mondrake. Opened 📌 Additional tests for DriverSpecificSchemaTestBase Active per your comment.

The last submitted patch, 2: 3355841-2.patch, failed testing. View results →

bot fluke

Committed 7d9c51d and pushed to 11.x. Thanks!

Cherry picked to 10.1.x

I think addressing #4 in a followup feels like a reasonable compromise.

Automatically closed - issue fixed for 2 weeks with no activity.