You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current approach adds more abstraction that is currently needed which makes it harder to debug database related issues. Furthermore there are problems with our internal API (Statement Wrapper) whose multiple return types (bool, Statement) cause some headaches when trying to close cursors properly for the most common cases, see #14459
Current status
Currently the classes that you typically use are called in the following order when running a method on the mapper class
Mapper
IDb
Db
StatementWrapper
IDBConnection
Connection
The goal is to get it down to this:
Mapper
IDBConnection
Connection
How can we do this?
Instead of requiring an instance of IDb for the Mapper, we are going to require an IDBConnection. In order to stay compatible until this can be removed after deprecation, we are going to do the following:
Mapper class will be adjusted to use IDBConnection and the methods on that class
Statementwrapper will be removed from Db
At some point we will be able to return an instance of IDBConnection from the ServerContainer instead of IDb to finish the migration and finally remove the code.
The current approach adds more abstraction that is currently needed which makes it harder to debug database related issues. Furthermore there are problems with our internal API (Statement Wrapper) whose multiple return types (bool, Statement) cause some headaches when trying to close cursors properly for the most common cases, see #14459
Current status
Currently the classes that you typically use are called in the following order when running a method on the mapper class
The goal is to get it down to this:
How can we do this?
Instead of requiring an instance of IDb for the Mapper, we are going to require an IDBConnection. In order to stay compatible until this can be removed after deprecation, we are going to do the following:
At some point we will be able to return an instance of IDBConnection from the ServerContainer instead of IDb to finish the migration and finally remove the code.
@DeepDiver1975 @MorrisJobke @PVince81 @LukasReschke @butonic @icewind1991 @georgehrke @jbtbnl
The text was updated successfully, but these errors were encountered: