Branch copy has old schema version
Hi 👋
I have an issue that a new branch does not include all columns of the base branch.
Workspace ID:
5713tr
New branch: test-template
Base branch: dev
test-template has previously existed, and I recreated it soon after deleting it. Could it be that it was restored instead of recreated?
Edit: This is a postgres enabled database.5 Replies
Hi Michael, thanks for reaching out. We'll take a look.
Which database is this branch on?
Nevermind, found it 👍
Which tables are affected? I see there are some tables missing as well. I'll keep digging.
Oh, sorry, didn't mention that.
column eventSeries.languages does not existNo worries. Could be a restore given the number of tables that are missing between
dev and test-templateInteresting. I've just created
test-template2 and it had the same issues. Then I've tried a completely new name, I'm sure never existed something-new and both those branches are missing the new columns. It seems that it's not about the target's branch name, but there's an issue reading the base branch.
FYI: I will now directly alter the schema for test-template2 using PSQL while you are investigating (to work on what i need to work on :P). OK?Yes that's fine Michael, thanks for the added info. I can create branches through the support access myself so we can continue to investigate. I'll keep you posted.
Identified the issue, we're working on a fix, thanks for bearing with us, Michael.
Hi Michael, thanks for bearing with us. We've pushed a fix for this issue (I tested it there with the
support-test-1 branch). One slight caveat, however; the dev branch has a long migration history, so branches created off it take time to complete. When you create a branch off of dev you may notice a timeout and an initial discrepancy in the tables. If you wait a few minutes and refresh the page, the branches will match. We're looking to improve this experience moving forward but the root issue has been resolved.