I'm reporting a significant performance issue and a potential for deadlocks when using Spring Batch with a SQL Server database. The root cause is a data type mismatch between the default Spring Batch ...

I need to query against a column which contains build numbers stored as an NVARCHAR.<BR>Sorting works fine until you get into double-digit versions.<BR><BR>This works ...