Fix MySQL 8.0.19+ integer display width compatibility

[metowolf]

Summary

This PR fixes the false positive schema differences when comparing between MySQL 5.7 and MySQL 8.0.19+, addressing issue #78.

Problem

MySQL 8.0.19+ deprecated and removed the display width for integer data types:

• MySQL 5.7: int(11), bigint(20), tinyint(1)
• MySQL 8.0.19+: int, bigint, tinyint

This causes constant false positives when syncing schemas between different MySQL versions, as the tool reports differences even though the column definitions are functionally equivalent.

Solution

Added a normalizeIntegerType() function that:

• Removes display width from integer types for consistent comparison
• Preserves type modifiers like unsigned, zerofill, unsigned zerofill
• Handles all integer types: tinyint, smallint, mediumint, int, bigint
• Case-insensitive matching for robustness

Updated FieldInfo.Equals() to use normalized type comparison, ensuring int(11) and int are treated as equivalent.

Changes

• internal/util.go: Add normalizeIntegerType() function with comprehensive documentation
• internal/db.go: Update FieldInfo.Equals() to use normalized integer type comparison
• internal/util_test.go: Add 30 unit tests covering all integer types and edge cases
• internal/field_test.go: Add 10 integration tests for field comparison scenarios

Test Coverage

All tests pass with comprehensive coverage:

• Basic integer type normalization (int, bigint, tinyint, etc.)
• Type modifiers (unsigned, zerofill, unsigned zerofill)
• Cross-version compatibility scenarios
• Non-integer types (varchar, text, etc.) remain unchanged
• Case-insensitive matching

Closes

Fixes #78

🤖 Generated with Claude Code