Jan-
No need to apologize!
One of my favorite things about open source is that we solve problems for each
other and can improve on each solutions.
I’m really glad you took the time to move those mid rewrite params out into a
separate profile and even happier that there was automation for it
Seconded. Definitely +1 if you can do that migration in SQL. I think it's
possible, but not easy. CTEs/With should help. But I wouldn't be -1 on (2)
if you decide (1) isn't feasible.
On Thu, Sep 14, 2017 at 10:20 AM, Jan van Doorn wrote:
> The go migration is my fault…. I couldn’t figure out how
The go migration is my fault…. I couldn’t figure out how to do some of that
stuff in SQL, and I think anyone would be hard pressed to do that.
Wasn’t aware we need the go compiler for that when I went down that path
though.
Maybe another alternative is to make a “light migration”? Here’s my t
As we’re moving to TC2.1, we’ve found that the goose migration requires not
just the goose binary to be installed, but also the go compiler and a fairly
large set of dependencies. Most of these are a result of the migration of the
MSO parent_retry parameters from the DS table into the profile_pa
