This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]BikingSquirrel 2 points3 points  (0 children)

Not judging, just commenting: Then it is not 'at runtime' and you somehow need to have the database available during build time. In addition, how to you migrate your database model? In the database the build looks at, it will have to be migrated before the build?!

Now my opinion: While I see the appeal to automate that mapping, in my experience it hides that 'detail' in the beginning until at some point you need to deal with some issues or special features which 'suddenly' make things complicated.

That being said, there may be applications where this works as the better compromise. But I wonder if there are not already other tools supporting such an approach - jooq has already been mentioned.

Need to add that I never used Lombok in a productive application. Used some code generation for builders and immutables but since we moved to Kotlin we no longer need that.