StoredProcedure enhancement to allow parameters to be optional [SPR-3510]

[spring-projects-issues]

toddmcgrath opened SPR-3510 and commented

Extending StoredProcedure is working great.

public SampleStoredProcedure(DataSource dataSource, String sprocName) {
    super(dataSource, sprocName);
    declareParameter(new SqlReturnResultSet("rs", new EventMapper()));
    declareParameter(new SqlParameter("EventTitle", Types.VARCHAR));
    declareParameter(new SqlParameter("EventType", Types.VARCHAR));
    declareParameter(new SqlParameter("StartDate", Types.DATE));
    declareParameter(new SqlParameter("EndDate", Types.DATE));
    declareParameter(new SqlParameter("Location", Types.VARCHAR));
    declareParameter(new SqlParameter("MinPrice", Types.INTEGER));
    declareParameter(new SqlParameter("MaxPrice", Types.INTEGER));
    compile();
}

There are times when I don't want to supply a MinPrice, MaxPrice values and use the defaults I've set in the sproc. But, I can't figure out how to avoid having to set every parameter declared. Know what I mean? Example- if I set 5 of the parameters in the map, I receive an exception about requiring 7 inputs.

Forum Reference: http://forum.springframework.org/showthread.php?t=39086

---

Issue Links:

• Support for named parameters in SimpleJdbcCall [SPR-12801] #17398 Support for named parameters in SimpleJdbcCall
• Support named parameters in CallableStatementCreator implementation [SPR-4406] #9084 Support named parameters in CallableStatementCreator implementation

12 votes, 8 watchers

[spring-projects-issues]

Juergen Hoeller commented

We should decide on this for 2.5.2 as well, Thomas...

Juergen

[spring-projects-issues]

Guram Savinov commented

There is no progress for this feature request since 2007 year, will you work on it in near future?
Check this idea on StackOverflow about how you can implement it: http://stackoverflow.com/questions/22618251/implementing-a-stored-procedure-call-with-optional-parameters-in-spring-3-0

[spring-projects-issues]

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.