Affected rows count in sql log is always zero if using Scan method

[caelansar]

Description

If using Find method to query

db.Table("user").Where("id=?", 1).Find(&user)

The sql log is:

[2.470ms] [rows:1] SELECT * FROM `user` WHERE id=1

While change Find to Scan method

db.Table("user").Where("id=?", 1).Scan(&user)

The sql log is

[2.206ms] [rows:0] SELECT * FROM `user` WHERE id=1

The affected rows count in Scan method is always zero, same issue for Row and Rows method. It because inside Scan method it calls Rows method, iterate the returned *sql.Rows and calculate affected rows count in ScanRows method after the sql log is already printed

[github-actions]

The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 2 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨