fix: update cobra command version string to 1.9.2

[ajitpratap0]

Fixes version inconsistency flagged by Claude review on PR #353.

cmd/gosqlx/cmd/root.go:126 still had Version: "1.9.0" — now corrected to "1.9.2".

[claude]

Claude finished @ajitpratap0's task —— View job

---

PR Review: Version String Update

Todo List:

• Read the modified file to understand the change
• Check for version-related tests that might need updates
• Analyze code quality, bugs, performance, and security
• Provide comprehensive review feedback

Review Summary

✅ Overall Assessment: This is a straightforward version string fix that correctly addresses the inconsistency flagged in PR #353.

Code Quality & Best Practices

✅ Positive:

• Clean, targeted fix addressing a specific version inconsistency
• The change is consistent with other version declarations in the same file (var Version = "1.9.2" at line 38)
• Maintains semantic versioning format (1.9.2)
• No functional logic changes, minimizing risk

Issues Found

⚠️ Additional Version Inconsistencies Detected:

I found several other files that still reference version 1.9.0 and should be updated for complete consistency:

1. cmd/gosqlx/doc.go:27 - Comment references "Current version: 1.9.0"
2. doc.go:19 - Documentation mentions "GoSQLX v1.9.0"
3. cmd/gosqlx/cmd/doc.go:344 - Comment shows Version = "1.9.0"
4. pkg/cbinding/cbinding.go:38 - Comment example shows version "1.9.0"

Security & Performance

✅ No concerns - This is a simple string constant change with no security or performance implications.

Test Coverage

✅ No test updates required - Version strings are typically not unit tested, and I found no version-specific test assertions that would be affected.

Recommendations

1. Consider updating all version references for complete consistency across the codebase
2. Future improvement: Consider using a single source of truth for version strings (e.g., a shared constant) to prevent such inconsistencies

Conclusion

This PR correctly fixes the immediate issue at cmd/gosqlx/cmd/root.go:126. The change is safe and appropriate, though there are additional version references that could be updated in a follow-up for complete consistency.

Approval Status: ✅ Ready to merge (with optional follow-up for remaining version references)