search

oysterprotocol / brokernode

Server that connects to the Tangle to enable the Oyster Protocol
36 stars 9 forks source link

[Brokernode] Move all .fizz migrations to .sql migrations #407

Open rfornea opened 6 years ago

rfornea commented 6 years ago

Rebel [7:15 PM] Hey I need to run only a certain migration, or I need to change our migrations to where it will only create the table if it does not already exist. Preferably the latter.

What are my options for this?

Mark Bates [7:28 PM] @Rebel yes and no. Nothing in fizz, but you can write a sql file as a migration as well. Then you can customize it fully.

Rebel [7:29 PM] Okay. In the meantime, is there a way to run just one migration?

Mark Bates [7:29 PM] No, sorry.

Rebel [7:29 PM] Ok

rfornea commented 6 years ago

When I originally encountered this table already exists error, it was when I was first setting up the prod brokers with their aurora DBs and deploying to production. But, I only ever encountered this error with the prod brokers.

Alex F set us up another aurora DB today and Nicolas tried to reproduce the error using similar conditions that created the error on the prod brokers. But, we cannot get the error to reproduce. Maybe buffalo or fizz has been updated since then, or maybe there was some other reason why I was getting this error before.

Anyway I don't think we need to worry about this issue for now, I think we can close it.

@nepeckman Do you have anything else to add?

vepeckman commented 6 years ago

Nah that sums it up. We spent a while trying to reproduce the error and couldn't get it to occur. Happy to pick this back up if the error reoccurs, spent a while getting familiar with the issue.

rfornea commented 6 years ago

I wish I'd taken a screenshot of the error or copied to a text file. It happened a number of times. Anyway closing for now.

rfornea commented 6 years ago

@pzhao5 This is the issue.