The current implementation of DibiAdapter supports Dibi 2 and 3. However, to support the 2.x branch, it relies on non-namespaced Dibi classes, Dibi\Driver::escape() method and possibly other things that have been deprecated in 3.0 and will be removed in 4.0 which seems to have entered beta stage recently.
Isn't it time to drop Dibi 2.x support? What do you think?
The current implementation of
DibiAdapter
supports Dibi 2 and 3. However, to support the 2.x branch, it relies on non-namespaced Dibi classes,Dibi\Driver::escape()
method and possibly other things that have been deprecated in 3.0 and will be removed in 4.0 which seems to have entered beta stage recently.Isn't it time to drop Dibi 2.x support? What do you think?