Gorm: strings slice causes goroutine to panic

Created on 12 Jan 2014 · 5Comments · Source: go-gorm/gorm

hi, just create a simple model that uses []string and it'll crash with something like this https://gist.github.com/AvianFlu/4688697c15b3587623a2

ie:

type User struct {
  Id int64
  Name string
  Emails []string
}

Source

yawnt

Most helpful comment

@jinzhu, would you be willing to show an example of how to make something like the above example work? I'm working on creating an API, and it would be much more succinct to have something like:

{
    "name" : "Test",
    "products" : [ "product1", "product2" ]
}

As opposed to the current way of doing it:

{
    "name" : "Test",
    "products" : [
          {  "value" : "product1"  },
          {  "value" : "product2"  }
}

Any help would be appreciated!

jordan-wright on 30 Apr 2014

👍4

All 5 comments

hi gorm doesn't support []string because database dialect that you are using don't know how to store it to database.

So maybe you need to write a Scanner for slice.

jinzhu on 14 Jan 2014

@jinzhu, would you be willing to show an example of how to make something like the above example work? I'm working on creating an API, and it would be much more succinct to have something like:

{
    "name" : "Test",
    "products" : [ "product1", "product2" ]
}

As opposed to the current way of doing it:

{
    "name" : "Test",
    "products" : [
          {  "value" : "product1"  },
          {  "value" : "product2"  }
}

Any help would be appreciated!

jordan-wright on 30 Apr 2014

👍4

I meet this issue too.

xubing on 27 Jul 2016

Yea, I'm running into this issue as well, and I have seen a bunch of old issues about this as well.
@jinzhu you've mentioned writing a Scanner or a Valuer for this situation. Do you mind expounding on what you are referring to? Maybe a link to an example.