Hi,
i currently start to use the Data Module and one thing isn't really nice.
If you have an abstract Repository, you likely have an import of
javax.persistence.Query and maybe @Query.
What do you think about renaming @Query to resolve the naming conflict?
Regards,
Thomas
You will not get it using TypedQuery ;).
@Query is the smoother default IMO
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-05-26 16:22 GMT+02:00 Thomas Andraschko
well, honestly more abstract repo are promoted less they seem useful.
interfaces are where the real added value is then some interceptors (for
audit for instance) are nice but no more. Abstract repo are technically
interesting but for app code they seem just a debt, no? What would be the
real use
At least for me, it's typically when the findByExample doesn't work anymore
(date range searches etc).
On Mon, May 26, 2014 at 5:21 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
well, honestly more abstract repo are promoted less they seem useful.
interfaces are where the real added
Ok, so I'd go for TypedQuery.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-05-26 17:38 GMT+02:00 Thomas Hug thomas@gmail.com:
At least for me, it's typically
