So we need a step before those because we currently do
"INSERT INTO libdep VALUES (?, ?, ?)"
which won't work with multiple columns I don't think (though
I haven't tested.) That means the first step would be to land
a change that altered that.
I don't want to block you on all of this though Michael, so I'd
be +1 on going ahead with a managed rollout of this change
with lockstep db migration, and to start to work on these
issues so we can do better with the next change.
Hi,
So we need a step before those because we currently do
"INSERT INTO libdep VALUES (?, ?, ?)"
which won't work with multiple columns I don't think (though
I haven't tested.) That means the first step would be to land
a change that altered that.
I don't want to block you on all of this though Michael, so I'd
be +1 on going ahead with a managed rollout of this change
with lockstep db migration, and to start to work on these
issues so we can do better with the next change.
Thanks,
James