Well said. I spent hours yesterday setting up a bunch of ORM make-work, rather than getting a connection to the DB and just doing a bloody query, for a "spell check" function.
All I needed to do was get the intersection of the set of user provided words (candidates) and the set of approved words (a text column in a dictionary table). Conceptually, I needed a prepared statement or query build to do something like:
select dict.word
from dict
where dict.word in ( ... candidates ... )
(the difference of the candidate set minus the result set being the unrecognized words)
But I had to drag in entity models with magic incantations, er, annotations, and repositories and a predicate factory class and multiple config files -- for a dictionary table that is rarely if ever updated, manually; it exists for this query. Sadness.
If I knew the Spring/Hibernate/JPA stuff better, it of course would have been easier, but what a pile of tripe to have to read through for the life of the project.
All I needed to do was get the intersection of the set of user provided words (candidates) and the set of approved words (a text column in a dictionary table). Conceptually, I needed a prepared statement or query build to do something like:
(the difference of the candidate set minus the result set being the unrecognized words)But I had to drag in entity models with magic incantations, er, annotations, and repositories and a predicate factory class and multiple config files -- for a dictionary table that is rarely if ever updated, manually; it exists for this query. Sadness.
If I knew the Spring/Hibernate/JPA stuff better, it of course would have been easier, but what a pile of tripe to have to read through for the life of the project.