For anyone stumbling onto this: a better way to do the @Repository is to use `public interface ParentRepository extends JPARepository` and the child class repository will be `public interface ChildRepository extends ParentRepository`
Is it considered a best practice to send a boolean as a parameter to the constructor like that? In my opinion, it is better to have a boolean to hold the status of the cab type(sleep cab or not) and enum with two values( e.g: enum truckCabType{NO_SLEEP_CAB, WITH_SLEEP_CAB} ) then the constructor will ask the parameter of type truckCabType instead of a boolean and will finally set the boolean internally depending on the received value; the class can have a probably method hasASleepCab() to return the boolean. Without the help of the IDE with the super useful parameter hints feature nobody will know what the "true" or "false" is for if the person who reviews the code doesn't check the method signature first. It's worth pointing that out given that people are relying heavily upon this kind of video to learn how to code so it is sometimes useful to show some best practices(or what I believe to be a best practice) while coding.
How to filler frontend details to subclasses with considering super class 's attribute ? It mean from vehicle class, considering seats. How devide details to trunk and truck?
Hey there! Can I define associations(@ManyToOne, @ManyToMany, @OneToMany, @OneToOne) in @MappedSuperclass? I actually tried it, but the problem is when hibernate generates schema, it doesn’t add @Basic fields in inherited tables.Can I fix it, or should I use completely different approach(use some kind of @Inheritance, for instance)?
For anyone stumbling onto this: a better way to do the @Repository is to use
`public interface ParentRepository extends JPARepository`
and the child class repository will be
`public interface ChildRepository extends ParentRepository`
@MappedSuperclass is sweet!
Yes, it is! :)
Is it considered a best practice to send a boolean as a parameter to the constructor like that? In my opinion, it is better to have a boolean to hold the status of the cab type(sleep cab or not) and enum with two values(
e.g: enum truckCabType{NO_SLEEP_CAB, WITH_SLEEP_CAB} ) then the constructor will ask the parameter of type truckCabType instead of a boolean and will finally set the boolean internally depending on the received value; the class can have a probably method hasASleepCab() to return the boolean. Without the help of the IDE with the super useful parameter hints feature nobody will know what the "true" or "false" is for if the person who reviews the code doesn't check the method signature first. It's worth pointing that out given that people are relying heavily upon this kind of video to learn how to code so it is sometimes useful to show some best practices(or what I believe to be a best practice) while coding.
Huge thank Sir!
You are welcome!
JpaRepository or CrudRepoditory? Thanks, super tutorial!!
Depends what you need, one is sub type of another and has some more stuff
super clear , thx
Great to hear!
How to filler frontend details to subclasses with considering super class 's attribute ? It mean from vehicle class, considering seats. How devide details to trunk and truck?
What is the difference between @MappedSuperClass and @Embeddable? I see that both of them do the same work, isn't it?
tanks !
You are welcome!
Hey there! Can I define associations(@ManyToOne, @ManyToMany, @OneToMany, @OneToOne) in @MappedSuperclass? I actually tried it, but the problem is when hibernate generates schema, it doesn’t add @Basic fields in inherited tables.Can I fix it, or should I use completely different approach(use some kind of @Inheritance, for instance)?
I think its not possible to use it with @MappedSuperclass