formalize db patches

[disaacson]

make clear way to create and update db to latest schema

[gregghz]

Is this for piezo admin? or for the worker?

[lucidchart]

yes

On Mon, Aug 22, 2016 at 9:46 AM Gregg Hernandez notifications@github.com
wrote:

Is this for piezo admin? or for the worker?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCfDjJODP1CXj7EMa8vVE3BzQAuL4Flks5qicRmgaJpZM4JqAow
.

[disaacson]

They share the same DB. So, yes. ;)

On Mon, Aug 22, 2016 at 9:46 AM, Gregg Hernandez notifications@github.com
wrote:

Is this for piezo admin? or for the worker?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABc3aK0E2UJhwJIzIK6aoBMFi61gUblAks5qicRngaJpZM4JqAow
.

[gregghz]

Oh. If it was just admin, I was going to say use play's evolutions: https://playframework.com/documentation/2.3.x/Evolutions

But it might not make sense to handle patches in the play project if they both use them. Or it might make sense. I don't know.

[lucidchart]

good idea

On Mon, Aug 22, 2016 at 10:14 AM, Gregg Hernandez notifications@github.com
wrote:

Oh. If it was just admin, I was going to say use play's evolutions:
https://playframework.com/documentation/2.3.x/Evolutions

But it might not make sense to handle patches in the play project if they
both use them. Or it might make sense. I don't know.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#61 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADCfDozGscEb9-V-qHHnPiv3OLco2NbVks5qicrtgaJpZM4JqAow
.

[pauldraper]

+1 for Play's evolutions.

It's a good system, and fairly easy.