😼 mogge

morning!

Morning

morning

morning

Morning everyone ☕

Hope you are all spiffingly wonderful today 🙂

well.. fighting with an SQL database... not much fun.... trying to delete an entry... but keep running into constraints that mean you can't just do a delete...

no cascading delete available @thomas ?

h,mmmm let me find out...

(I didn't setup that DB...)

cascading delete isn't used anywhere 😞

what flavour of db is it ?

mysql

looks like you need to enable it when creating the tables...

you can probably do an alter-table to add the cascade to the constraints...

let me try that....

how much do you care about keeping consistency? You can just turn off constraints in MySQL 😄

(it is test data only anyway at the moment... so recreating wouldn't be a problem anyway) not sure if they want it in production though.

I don't care about consistency what so ever! 😈

https://stackoverflow.com/a/15501754/173062

@glenjamin actually I am quite tempted to do that... 😉

at least my tests would be simpler to write in that case.

Doooo Eeeeeet!

😉

👍

I mean.... what is the worst that can happen?

why not just fix the schema, then you will have no problems now or in the future ?

The customer might not like us changing the DB schema, it is an existing schema already in prod at the moment.

( we write the tests after we have done all the code of course 😱 )

presumably there will be migrations on the schema ? i just counted 139 migrations on my db schema over the last 2 years!

@mccraigmccraig Out of interest, what are you using for migrations? ragtime?

Something you’ve stuck with for that long must be a good choice. 🙂

@chrisjd i'm using https://github.com/macourtney/drift - if i was starting again i would probably try ragtime or joplin, but i was familiar with drift from an earlier project and had already patched it to my needs (those being cassandra and elasticsearch)

Interesting, thanks.

drift doesn't do an awful lot - it creates template migration namespaces with up/down fns and calls them in order - you give it a couple of fns which it uses to determine current migration state and to set up for running migrations, so it's easy to adapt to any old datastore

in my migration namespaces i just call my regular db connectors... all very straightforward

e.g. https://gist.github.com/mccraigmccraig/dbf2b2144da95079489309a3ca4c3b6d

joplin and ragtime look like they have approaches to dealing with conflicts though, which is probably the major pain point

i’ve used simple migration tools for years without really seeing many/any issues

if you get conflicts at the schema level you’re probably not talking/integrating enough?

@glenjamin the conflicts i'm thinking of come from merging branches resulting in interleaving of migrations from each branch

but maybe those are not the conflicts that joplin/ragtime are talking about... dunno

i assumed the same

but either you have disparate teams editing the same schema, which is bad

or you have a single team which isn’t talking enough, which is bad

there's a third option 🙂

oh, i see - ragtime’s definition of conflict is more broad than i expected

generally I’d expect interleaved migrations is only an issue if you both touch the same part of the schema, and if there’s a chance that this could happen you should probably get the migrations merged into the mainline quickly and released even while development is still ongoing

yeah, i generally end up doing a rebase, but manually

and i don't have the option of adding stuff to the mainline at arbitrary times - my clients are mostly apps and apple's review process imposes fairly rigid release constraints

I was thinking more about the mainline development branch

ie. make everyone else on the team aware ASAP

My assumption has always been that ragtime’s apply-new is how migration runners work (ever since i used the one in rails)

ah, i see, yeah that could work - rebasing works too though

Afternoon

afternoon

afternoon!

good afternoon 🙂

🍵

🍰