The _update_batch() method is missing from the Postgre database driver in the latest stable release of CI, 2.1.3. It IS in the 3.0 repo already.
I am unfamiliar with the current updates of the Postgre driver (I can see clear differences between 2.1.3 and 3.0), nor do I have any Postgre testing abilities, or I would try to patch this quickly myself. I don't just want to copy and paste under any false assumptions that it'll plug and play. If anyone can specify a solution, I can implement it if necessary.
Which version did it exist in?
Looks like d06acd8 never got merged into the 2.1.3
@narfbg Probably best for this to get dealt with in 2.1.4 if it ends up being released or it'll get solved in 3.0 .
I don't know if this ever existed in a 2.x version; I just know that it is currently in 3.0.
I don't see a 2.1.4 release coming, 3.0 is most certainly the next one. With that said I'm indifferent on this one - marked it to be on the 2.1.x milestone, but I'm really not interested in backporting anything at this point.
You are of course free to submit it as a pull request for 2.1-stable.
If I had Postgre capabilities I would likely consider it, but based on the differences between the drivers as a whole, and me not having any way to test it, I'll have to leave that up to someone else if they so wish.
Any clue on a timeline for a 3.0 release?
Is anyone with Postgre support interested in doing a hot fix for 2.1.3 to make this work? Or, is there are more definitive timeline for 3.0 that suggests we should just wait a little bit? Just trying to clean up my outstanding issues.
Just assume there isn't support for this in 2.1.x. 3.0 could happen at any time and I don't see a 2.1.4 release coming.
Yeah I figured that's what would happen. It hasn't come up much, anyway, so it's obviously not a giant priority. Thanks for closing.