>
> I am confused how you are "mind mapping" PreparedStatement parameters and
> entity construction into the same conversation. We are not instantiating
> entities based on PreparedStatement parameters
>
I'm not sure I understand you, I haven't mentioned PreparedStatement
parameters anywhere
Hi all,
I have PTO until the end of the week. I’ll be checking email from time to time.
Cheers,
Koen
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
JPA says that portable applications (portable across JPA providers) should
have default constructor. Every provider supports things beyond the
spec. Heck JPA also says that getters and setters need to be public, but
we don't enforce that either.
On Mon, Mar 28, 2016 at 7:27 AM Vlad Mihalcea
wr
Nowadays the entity instantiation and data population is done like that:
final Object object;
if ( optionalObjectKey != null && key.equals( optionalObjectKey ) ) {
//its the given optional object
object = optionalObject;
}
else {
// instantiate a new instance
object = session.insta
Commented on the Jira.
I am confused how you are "mind mapping" PreparedStatement parameters and
entity construction into the same conversation. We are not instantiating
entities based on PreparedStatement parameters
On Fri, Mar 18, 2016 at 2:32 AM Lovro Pandzic
wrote:
> Hello,
>
> I'd lik
