Fix entries blueprint performance

[FrittenKeeZ]

Fixes #126

[FrittenKeeZ]

This needs to be re-run when 3.4.5 release is unbotched

[what-the-diff[bot]]

• Add blueprint column to entries table
• Migrate existing data from data field into new blueprint column
• Update Entry model and query builder to use the new database columns instead of reading/writing them in the JSONB blob

[maxi032]

@jasonvarga When are you guys going to merge this as we are also facing the same problems

[ryanmitchell]

@FrittenKeeZ I've just applied this to a 2.1.0 install and I would be worried people wont catch that they need to run the php please eloquent:migrate-entries-blueprint command unless they are keeping an eye on merged PRs.

Why don't we run it as part of the migration?

[FrittenKeeZ]

@ryanmitchell That's absolutely possible - I just had to have a way to keep updating the data over and over while getting it to work.

[ryanmitchell]

Great, leave it with me and I'll update