Can you explain why it is necessary to check io.EOF there?

CC @kardianos

For more information read documentation for type RowsNextResultSet interface and it is clearly mentioned that NextResultSet should return io.EOF when there are no more result sets.

Please look at https://bitbucket.org/kardianos/table for the proper way to use NextResultSet. I'm aware of how to use it and the documentation; I wrote it.

@kardianos, let me clear, i am new to database.

The reason behind escalating this issue is that i want to know in which case NextResultSet return true?

I tried all the cases using mysql database it is always returning false. If so then what is the use case of implementing NextResultSet?
Could you please give me at least one use case where NextResultSet return true.

Before giving your answer, i would suggest you to do sample program on NextResultSet where it can return true case.

I hope you got my Question.

If you are new to databases and want some clarifications, please take a look at the Questions wiki page to ask questions like these. You will get better and faster answers there. The issue tracker is primarily for bugs and proposals.

@agnivade, I understand your concern. I tried all the cases using mysql database, NextResultSet is always returning false. If so then it is bug right. So i am in right page for escalating this as an issue.

Its was my big mistake. There is NO issue in NextResultSet method.

I was working with different databases using golang sql package.
In PostgreSQL this NextResultSet method returns true using (github.com/lib/pq) even there is no multiple resultsets.
Sample program

I was thinking this same behavior with MySQL using (github.com/go-sql-driver/mysql)

Eventually i found unexpected behavior (or bug) of lib/pq

I filed an issue report on lib/pq.