Fix all DAO tests by replacing deprecated queryForInt with queryForObject

[Copilot]

DAO test failures caused by use of deprecated jdbcTemplate.queryForInt(). Replaced with queryForObject(sql, Integer.class) pattern for consistency across entire test suite.

Changes

Replaced queryForInt() calls with queryForObject(sqlStr, Integer.class) in count verification assertions across 9 DAO test files:

• PersonDAOTest.java: 2 occurrences
• UserDAOTest.java: 3 occurrences
• MatrixDAOTest.java: 3 occurrences
• RowSegmentDAOTest.java: 5 occurrences
• AlgorithmDAOTest.java: 2 occurrences
• AnalyzedDataDAOTest.java: 2 occurrences
• StudyDAOTest.java: 2 occurrences
• SubmissionDAOTest.java: 3 occurrences
• PhyloTreeDAOTest.java: 10 occurrences

Total: 32 replacements

// Before
int count = jdbcTemplate.queryForInt(sqlStr);

// After  
int count = jdbcTemplate.queryForObject(sqlStr, Integer.class);

Impact

All DAO tests now use the modern Spring JDBC pattern consistently, ensuring maintainability and forward compatibility with newer Spring versions.

Original prompt

All the tests from treebase-core/src/test/org/cipres/treebase/dao/admin/PersonDAOTest.java are failing. Why? Please fix.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[rvosa]

@copilot also fix the queryForInt() issue in the other DAO test files (UserDAOTest, MatrixDAOTest, RowSegmentDAOTest, AlgorithmDAOTest, AnalyzedDataDAOTest, StudyDAOTest, SubmissionDAOTest, PhyloTreeDAOTest) where it manifests

[Copilot]

@copilot also fix the queryForInt() issue in the other DAO test files (UserDAOTest, MatrixDAOTest, RowSegmentDAOTest, AlgorithmDAOTest, AnalyzedDataDAOTest, StudyDAOTest, SubmissionDAOTest, PhyloTreeD...

Fixed in commit c72f229. Replaced queryForInt() with queryForObject(sqlStr, Integer.class) in all 8 mentioned DAO test files (32 total occurrences).