search

spring-projects / spring-framework

Spring Framework
https://spring.io/projects/spring-framework
Apache License 2.0
56.22k stars 37.98k forks source link

Annotated Driven RowMapper Implementation [SPR-3805] #8485

Closed spring-projects-issues closed 12 years ago

spring-projects-issues commented 17 years ago

Marc Teufel opened SPR-3805 and commented

What about the Idea of implementing a RowMapper-Implementation that is able to read the column mapping between a Bean Property and the database Table Column via an Annotation. Using Annotations using sql alias to get an exact matching between a bean property name in BeanPropertyRowMapper that came in 2.1M1 is not needed anymore.

For instance a Annotation like

@SpringJdbcMapped setId

could match the Database Column "ID"

and

@SpringJdbcMapped(column="DATABASE_ID") setId

could match the Database Column "DATABASE_ID"

I have just implemented something like this, you can download it here --> http://javamagazin.de/itr/ausgaben/psecom,_psframe,,linkobject,source_,id,365,nodeid,20.html (look at "Datenbankzugriff mit JDBC und Spring (Marc Teufel)" Here you can Download my AnnotatedRowMapperResultReader including samples.

As I am using SpringJDBC like hell in my applications I am looking forward seeing something like this in 2.1 ! Hope you like that idea too ...

Cheerio Marc

Affects: 2.1 M3

spring-projects-issues commented 12 years ago

Rossen Stoyanchev commented

This issue has been resolved through a selective bulk update, as part of a larger effort to better manage unresolved issues. To qualify for the update, the issue was either created before Spring 3.0 or affects a version older than Spring 3.0 and is not a bug.

There is a good chance the request was made obsolete, or at least partly outdated, by changes in later versions of Spring including deprecations. It is also possible it didn't get enough traction or we didn't have enough time to address it. One way or another, we didn't get to it.

If you believe the issue, or some aspects of it, are still relevant and worth pursuing at present you may re-open this issue or create a new one with a more up-to-date description.

We thank you for your contributions and encourage you to become familiar with the current process of managing Spring Framework JIRA issues that has been in use for over a year.