Title: Why does Spring Data JDBC use reflection in PersistentPropertyAccessor, and could code generation improve performance?

Question: I'm currently working with Spring Data JDBC, and I've noticed that PersistentPropertyAccessor relies on reflection to access and manipulate properties. I understand that reflection can be slow, and I'm wondering why this choice was made.

1. What are the reasons behind using reflection in PersistentPropertyAccessor in Spring Data JDBC?

2. Have there been any performance considerations taken into account when choosing reflection as the method for property access?

3. Could using code generation tools like MapStruct provide a performance improvement in this context, and are there any trade-offs to consider?

   I'm interested in understanding the design decisions and potential performance enhancements related to this specific aspect of Spring Data JDBC. Any insights or best practices in this area would be greatly appreciated.