Why not integrate Exposed with the Spring Data ins...
# springo
orangy
10/13/2018, 3:09 PM
Why not integrate Exposed with the Spring Data instead? You’re suggesting essentially forking DSLs and fragmenting community
👍 2
o
oshai
10/13/2018, 3:29 PMI am pro to not fragmenting community, what about squash?
s
sdeleuze
10/13/2018, 3:39 PM1) Exposed seems not an officially supported project.
2) It is mainly based on Active Records pattern which I don't like and don't want to use, so I am not talking about doing what Exposed does, just I like the SQL DSL without code generation idea. Also I think there is also things I would implement differently to make people with Spring background confortable with it.
3) I think it should be possible to use SQL DSL independently of the underlying engine that perform the request.
sdeleuze
10/13/2018, 3:41 PMLike there is various opinions on Kotlin web frameworks, there could be different opinions on Kotlin idiomatic SQL persistence.
sdeleuze
10/13/2018, 3:42 PMEven if they model the same domain
👍 1
n
nfrankel
10/13/2018, 3:51 PM@orangy i believe competition is good
people should have choice so they can decide what fit best their context
(i don’t know about exposed, i don’t judge it in any way)
6 Views