Add expert analysis on posts/meta vs dedicated migrations #15
+820
−57
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Comprehensive analysis document covering: - Current EAV architecture evaluation - Performance benchmarks and comparison matrix - Hybrid approach recommendation (dedicated tables by default) - Migration strategies for existing installations - Implementation plan in 4 phases - Field-to-column mapping recommendations - Backward compatibility considerations
This implements the plan from improvements_for_posts.md to favor dedicated migrations over the WordPress-style posts/meta (EAV) pattern. Changes: - Update MakeResource command with --dynamic and --no-migration flags - Auto-generate migrations when creating resources with custom tables - Add $usesMeta = false to custom resource stub - Add tableColumnType to field classes for migration generation: - Boolean: boolean - Image, File, Repeater, Json, Checkbox: json - Time: time - Code: text - Enhance CreateResourceMigration command: - Skip structural fields (Tab, Panel, etc.) - Skip relationship fields using pivot tables - Add --soft-deletes and --no-timestamps flags - Output table summary of field-to-column mapping - Add composite indexes for common queries - Update config with better documentation and AURA_CUSTOM_TABLES env var - Update CLAUDE.md with database storage patterns documentation The default behavior remains unchanged (posts/meta) for backward compatibility. Set AURA_CUSTOM_TABLES=true to use dedicated tables by default.
- Change default value of custom_tables_for_resources to true - Existing installations can set AURA_CUSTOM_TABLES=false for backwards compatibility - Update documentation to reflect new default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Comprehensive analysis document covering: