Leftmost: it turns out that with an eye on bringing BB into the MB architecture in 2019, it might be a problem that BB moves to Portgres 10.
2018-11-28 33257, 2018
Mr_Monkey
What are the issues that you are running into for the BB schema changes? Is it only renaming the enum values?
2018-11-28 33257, 2018
Mr_Monkey
And follow up question for everybody around: does anyone have a trick to rename enum values in postgres 9.5 ? :)
2018-11-28 33255, 2018
Mr_Monkey
(I know we all collectively agreed there was no reason why not to move BB to psql 10, but apparently we had a collective brainfart, sorry)
2018-11-28 33235, 2018
Leftmost
Yeah, that occurred to me. The enum rename is the only real issue. There are tricks to cast to a new enum, but they all seem to rely on text values, which doesn't actually help.
2018-11-28 33202, 2018
Mr_Monkey
I think our three options right now are
2018-11-28 33202, 2018
Mr_Monkey
1) Find a way to do the migration using v9.6 — suggestions welcome
2018-11-28 33202, 2018
Mr_Monkey
2) Leave the enums as-is until MeB moves to v10
2018-11-28 33202, 2018
Mr_Monkey
3) Use a postgres container separate from MeB
2018-11-28 33202, 2018
Mr_Monkey
#3 is the one I abhorre most, and I would consider it a blocker to reaching our MVP.
2018-11-28 33202, 2018
Mr_Monkey
Let's see if anyone has suggestions for #1, and if not, see how we can live with #2
2018-11-28 33256, 2018
ruaok
enums are not really a good enough reason to cause the pain to wait for PG 10.
2018-11-28 33222, 2018
ruaok
let's find another way of solving this problem for now -- once we get to 10, then we can fix the enums properly.
2018-11-28 33251, 2018
Mr_Monkey
ruaok: By waiting for PG 10, I mean keeping the enum labels as-is instead of renaming them (Creator->Author for example)
2018-11-28 33253, 2018
Leo_Verto
would using a newer version of the same container be an option?
2018-11-28 33213, 2018
Leo_Verto
i.e. use a VAR for the postgres version and select that at container build time, then tag the container appropriately
2018-11-28 33255, 2018
CatQuest
[20:38] <Mr_Monkey> 2) Leave the enums as-is until MeB moves to v10
2018-11-28 33256, 2018
CatQuest
completely dumb non-coder user here
2018-11-28 33256, 2018
CatQuest
but that's my opinion? (fwiw)
2018-11-28 33226, 2018
CatQuest
the other two jsut seems like way too much hassle
2018-11-28 33229, 2018
Mr_Monkey
Leftmost knows what he's talking about, and I don't really, but if I'm not mistaken, the result would be that our website and ORM usean entity name that is different from the schema name. Ugly.
2018-11-28 33252, 2018
Mr_Monkey
But not a blocker, I suppose.
2018-11-28 33245, 2018
CatQuest
when is meb going to PG 10?
2018-11-28 33208, 2018
Mr_Monkey
CatQuest: I think that's a discussion for next Monday :)
2018-11-28 33237, 2018
george
Hey CatQuest! Just wondering whether you’ve hade the time to take a glance at my inst requests?
2018-11-28 33239, 2018
CatQuest
yea exactly. just wondered if the eta is sometime early first quarter 19 or halfway through, it's fine to wait on bb
2018-11-28 33246, 2018
CatQuest
erh it's fine for bb to wait
2018-11-28 33249, 2018
Leftmost
The enum rename isn't, I suppose, a blocker to schema change, as it won't have a user-facing effect.
2018-11-28 33257, 2018
CatQuest
george: hola! i am literally going trough those now :D
2018-11-28 33208, 2018
Leftmost
It just makes the schema change incomplete.
2018-11-28 33246, 2018
CatQuest
Leftmost: sounds unsatesfying. but as long as it doenst casue a problem later with scema change..
2018-11-28 33208, 2018
CatQuest
but then again, we should find out if it *will* becasue this sounds liek the kidn of thing that could casue a massive problem once it's time to update
INST-750: Krap-An instrument from Cambodia and Thailand
2018-11-28 33254, 2018
CatQuest
this has been doen itno the krap koo
2018-11-28 33202, 2018
Leftmost
Mr_Monkey, it won't, for a couple reasons.
2018-11-28 33229, 2018
george
For now, I’ll do a different instrument, but I’ll work with this student for those instruments on the side over the next couple of weeks (if that’s okay?)
2018-11-28 33235, 2018
CatQuest
so the other two are remaining krap puang and another for krap saepa.
2018-11-28 33242, 2018
CatQuest
that's totlaly ok
2018-11-28 33257, 2018
CatQuest
let's loo kat the work you've doen now (I also have a couple other tasks to look at)
2018-11-28 33206, 2018
CatQuest
oh george don't edit the "create clapper-tree" (INST-630) or other inst ticket unless i say it's ok, it's confusing for me :D
right. so this is what I'll do. can i sak you to make one other instrument ticket (since technically the other student made that instrument) and then hopwfulyl the two of you can work on the "krap" :D together
2018-11-28 33214, 2018
CatQuest
(like, lummi stikc is fine ;))
2018-11-28 33243, 2018
CatQuest
and I'll explain it to thme as well and approve both your tasks
2018-11-28 33205, 2018
CatQuest
and then you can go and do another thing
2018-11-28 33211, 2018
CatQuest
sound good?
2018-11-28 33234, 2018
CatQuest
oh yes "For now, I’ll do a different instrument, but I’ll work with this student for those instruments on the side over the next couple of weeks (if that’s okay?)"
2018-11-28 33235, 2018
CatQuest
yes that's great!
2018-11-28 33249, 2018
george
Perfect! I'll start researching a new instrument now then :)
2018-11-28 33206, 2018
CatQuest
(there are more on that clapper tree (hint hint) ) ;)
I need to go now, I can answer further questions later
2018-11-28 33242, 2018
dk joined the channel
2018-11-28 33235, 2018
c1e0 joined the channel
2018-11-28 33217, 2018
dk has quit
2018-11-28 33245, 2018
CatQuest
george: I'm going to "RMW" the ticket, and oyu cna re-submit it once you've doen that other instrument. it's late her and i need to sleep also. so I'll look at it in the morning :)
2018-11-28 33214, 2018
george
Sounds like a plan
2018-11-28 33219, 2018
CatQuest
👍 you're doing great work (I suspect you're getting sick of hearing this :P)
