Some ideas about sql2o HOT 5 CLOSED

Columns to Field mapping
the best way to make it versatile is GoF Strategy Pattern allowing any third-party tweaks via custom ColumnMappingStrategy implementation.

from sql2o.

Hi Dimzon,

Thank you very much for your suggestions.

I will definitely take a look at ReflectASM. Maybe do a test to see how much performance will improve. As you suggest, I also think it is important to be able to fall back to using java reflection.

I also agree that the QuirksMode solution is far from perfect. This is definitely open for improvements. I really like your suggestion; might be worth checking out.

Your other suggestions are good too, will consider them as well.

Thx!

Regards
Lars Aaberg

from sql2o.

I think it's closing time for this issue.
@dimzon leave a comment if you think we didn't cover everything.

from sql2o.

Some refactorings must be done in compatibility-breaking version
So auto-camel-case case-sensetivity custom-property-mapping must be re-implemented via GoF:Strategy pattern - ColumnMappingStrategy interface wich must obtain set of Pojo properies, set of ResultSet columns and return column->property binding pairs

from sql2o.

I agree. That is described in issue #83 .

from sql2o.