feat: ESPI 4.0 Schema Compliance - Phase 4: ReadingQuality #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements Phase 4 of ESPI 4.0 schema compliance, updating ReadingQuality to match the ESPI 4.0 XSD specification (espi.xsd:1062-1077).
Key Changes
ReadingQualityEntity:
Object, notIdentifiedObject@GeneratedValueto useIDENTITYstrategyqualityfield per XSD)ReadingQualityDto:
qualityfield matches XSD specificationReadingQualityMapper:
qualityfield mappingid,intervalReading)Flyway Migrations:
reading_qualitiestable from V3 to V2 vendor-specific filesBIGINT AUTO_INCREMENTBIGSERIALTest Plan
✅ All 550 unit and integration tests passing
Technical Details
XSD Reference: espi.xsd:1062-1077
Files Changed:
ReadingQualityEntity.java- Changed ID type to LongReadingQualityMapper.java- Simplified mappingsV3__Create_additiional_Base_Tables.sql- Relocated table, updated headerV2__MySQL_Specific_Tables.sql- Added reading_qualitiesV2__PostgreSQL_Specific_Tables.sql- Added reading_qualitiesV2__H2_Specific_Tables.sql- Added reading_qualitiesMigration Strategy
Related
🤖 Generated with Claude Code