FAQ
Why doesn't database/sql package define interface for return muti-result in
a query? some thing like MutiRows{}

It's common scenario to return muti result in a query. and it can be used
to return output parameter of store procedure.

And, suggest sql.rows/row can read column value by index or name, Scan(dest
...interface{}) is inconvenient.

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Daniel Theophanes at Jul 25, 2013 at 1:44 am
    I would also be interested in seeing such an API addition.

    Has anyone else found themselves needing:
      * Multiple result sets returned.
      * Named parameters.
    ?
    On Wednesday, July 24, 2013 6:38:50 PM UTC-7, buzzlight wrote:

    Why doesn't database/sql package define interface for return muti-result
    in a query? some thing like MutiRows{}

    It's common scenario to return muti result in a query. and it can be used
    to return output parameter of store procedure.

    And, suggest sql.rows/row can read column value by index or name,
    Scan(dest ...interface{}) is inconvenient.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Liigo Zhuang at Jul 25, 2013 at 7:08 am
    +1
    在 2013-7-25 上午9:44,"Daniel Theophanes" <kardianos@gmail.com>写道:
    I would also be interested in seeing such an API addition.

    Has anyone else found themselves needing:
    * Multiple result sets returned.
    * Named parameters.
    ?
    On Wednesday, July 24, 2013 6:38:50 PM UTC-7, buzzlight wrote:

    Why doesn't database/sql package define interface for return muti-result
    in a query? some thing like MutiRows{}

    It's common scenario to return muti result in a query. and it can be used
    to return output parameter of store procedure.

    And, suggest sql.rows/row can read column value by index or name,
    Scan(dest ...interface{}) is inconvenient.

    --
    You received this message because you are subscribed to the Google Groups
    "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Buzzlight at Jul 25, 2013 at 7:24 am
    1. sql.rows.Columns() can return data type of columns
    2. interface for store procedure and can get output parameter from result.



    在 2013年7月25日星期四UTC+8上午9时38分50秒,buzzlight写道:
    Why doesn't database/sql package define interface for return muti-result
    in a query? some thing like MutiRows{}

    It's common scenario to return muti result in a query. and it can be used
    to return output parameter of store procedure.

    And, suggest sql.rows/row can read column value by index or name,
    Scan(dest ...interface{}) is inconvenient.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJul 25, '13 at 1:38a
activeJul 25, '13 at 7:24a
posts4
users3
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase