container-transact about hawkreloaded HOT 5 CLOSED

Yeah the only issue with "omitting" this old value is we'll have to hardcode it out, which really drags down the maintainability and cleanness.

I might end up just removing it completely. The newer 1.7+ builds wont work correctly on prior databases anyways. And our datatypes all contain manually defined id's (Thank god we don't use ordinals xD).

from hawkreloaded.

Are these config options replaced by container-transaction? If so, should I set these options to false until they're removed? (I currently have them set to true.)

from hawkreloaded.

No the container-transaction variable is deprecated and has been replaced with container-insert and container-extract. Having container-transaction: true within the config wont change anything aside from storing the true value in memory for the container-transaction.

I'm most likely going to completely remove container-transaction from the next update as it's been completely replaced.

from hawkreloaded.

Oh ok so he's just been spelling it wrong and I somewhat misread. So container-insert and extract are the replacement nodes then?

from hawkreloaded.

Yes, they are a replacement. Sorry for my spelling mistakes, I'm not a native English-speaking person.

from hawkreloaded.