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
In Elegant Object Vol. 2, section 6.5.6 Too many round trips, Yegor discuss about the problem of many round trips to RDBMS, to fetch data from each SQL Speaking Object (SSO). A solution to this problem is use a FakeConnection class (here it will be called Cached) that will cache all data of each SSO. But to implement a caching decorator to JDBC API it isn't trivial. We need implement a SQL parser and analyser to check each SQL statement to perform correctly (store or retrieve) data.
The API to be used by the developer should be something like:
In Elegant Object Vol. 2, section 6.5.6 Too many round trips, Yegor discuss about the problem of many round trips to RDBMS, to fetch data from each SQL Speaking Object (SSO). A solution to this problem is use a
FakeConnection
class (here it will be calledCached
) that will cache all data of each SSO. But to implement a caching decorator to JDBC API it isn't trivial. We need implement a SQL parser and analyser to check each SQL statement to perform correctly (store or retrieve) data.The API to be used by the developer should be something like:
The text was updated successfully, but these errors were encountered: