FAQ
Hi,

I'd like to patch for structs like sql.NullInt16, sqlNullInt32.. etc to
improve the memory usage.

Just wondering why not adding sql.NullInt16, sql.NullInt32 to reduce the
memory allocation size? Is there any concern?

Thanks

Yo-An Lin

--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Carlos Castillo at Sep 22, 2013 at 10:08 am
    Are you ever going to have enough columns so that the size of a single row
    is a problem?

    The purpose of the sql.Null* types is to determine if the value of a column
    is null instead of the Zero Value, if it is important to know the
    difference. You only need to create one per necessary column to pass to
    rows.Scan(), use the value or null to fill you own data structures, and
    then re-use them for the next row.
    On Friday, September 20, 2013 11:04:52 AM UTC-7, c9s wrote:

    Hi,

    I'd like to patch for structs like sql.NullInt16, sqlNullInt32.. etc to
    improve the memory usage.

    Just wondering why not adding sql.NullInt16, sql.NullInt32 to reduce the
    memory allocation size? Is there any concern?

    Thanks

    Yo-An Lin
    --
    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 [email protected].
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedSep 20, '13 at 6:04p
activeSep 22, '13 at 10:08a
posts2
users2
websitegolang.org

2 users in discussion

Carlos Castillo: 1 post C9s: 1 post

People

Translate

site design / logo © 2023 Grokbase