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
{{ message }}
This repository was archived by the owner on Aug 29, 2022. It is now read-only.
This is an interesting project. I started exploring ktorm recently and was looking for ways that the mapping boilerplate could be reduced.
Do you think it makes sense to use JPA annotations (like @Entity, @Column etc.) instead of custom annotations like @KtormTable ? It will reduce learning curve for many people coming from java ecosystem and also the annotations are already well thought out.
I am not proposing that ktorm become a JPA provider. There are multiple other projects like EBean which use JPA annotations but are not full-fledged JPA providers.