Ghost/core/test/regression/api
Rishabh Garg 8ec12d9eee
🏗 Extracted post metadata in new post_meta table (#11102)
NOTE: The post metadata table split is purely an internal optimization for v3 and doesn't require or expect any external actions including related API usage in v3

We keep running into issues adding new fields to the post table because there are too many fields making the post table "too wide". We have also hit MySQL limitations in how many bytes can be in a row (64kb) with post table.

In v3, we decided to split the 8 post fields (meta, twitter and og) used for meta data into a posts_meta table as these 8 fields are all "problem" `varchar` fields and make sense logically grouped together. The API layer is unaffected by the split as input/output serializers ensure the data flow works the same way as it was in v2. Only thing to note is json export in v3 will have slightly different structure with posts meta fields as separate.

- Creates new post_meta schema/table with 8 fields (2 meta_* , 3 twitter_* and 3 og_*)
- Update relations between post and post_meta table
- Update input/output serializers to keep existing API behavior
- Avoids new entry in post_meta table for post where all meta fields are null
- Keeps the current fields API param behavior
- Handles migration of existing posts to new table structure
- Updates importer/exporter to work seamlessly with table changes
2019-09-16 14:15:55 +05:30
..
canary 🏗 Extracted post metadata in new post_meta table (#11102) 2019-09-16 14:15:55 +05:30
v2 🏗 Extracted post metadata in new post_meta table (#11102) 2019-09-16 14:15:55 +05:30
v3 🏗 Extracted post metadata in new post_meta table (#11102) 2019-09-16 14:15:55 +05:30
admin_spec.js 🔥 Removed all non-/ghost/ redirects to the admin 2019-09-11 14:55:00 +01:00