data class is preferable (see data class benefits)...

# spring

[deviant]

data class is preferable (see data class benefits). and middleName should be nullable type

[thanksforallthefish]

data class are not preferable, equals and hashcode are better off as db ids when thinking jpa

[deviant]

i use data classes with hibernate for years. what exact problems do you mean?

[kqr]

cant you override equals and hashcode in data class?

[Jason Feng]

Hi guys, thanks for the reply, which lead me to google more deeper into this, and I found this statement from Spring Data
Here we don’t use data classes with val properties because JPA is not designed to work with immutable classes or the methods generated automatically by data classes. If you are using other Spring Data flavor, most of them are designed to support such constructs so you should use classes like data class User(val login: String, …​) when using Spring Data MongoDB, Spring Data JDBC, etc.

[Jason Feng]

and here is the link https://spring.io/guides/tutorials/spring-boot-kotlin/#_persistence_with_jpa

[deviant]

i use models like this one a lot:

data class Funnel(
    @ManyToOne
    @JoinColumn
    @JsonIgnore
    val product: CompanyProduct,
    var name: String,
    @Enumerated(EnumType.STRING)
    var state: State = State.ACTIVE,
    val createdAt: Instant = Instant.now(),
    var updatedAt: Instant = Instant.now(),
    var archivedAt: Instant? = null,
    @Id @GeneratedValue
    val id: Long = 0
)

have no any problems so far

[Luis Munoz]

Same here but I am beginning to think that is because the problem is with hashing and equals which are used to knwo when to fetch an item from the db, which would be difficult to spot a problem