Gorm: Ignore flag not working on model struct?

Created on 1 May 2016 · 12Comments · Source: go-gorm/gorm

I have this model:

type User struct {
    gorm.Model

    // The Users username
    Username string `gorm:"size:255;unique;not null"`

    // The Users email address
    Email string `gorm:"size:255;unique;not null"`

    // The Users hashed password
    Password string `gorm:"size:255;not null"`

    // The Users password confirmation (only for forms)
    PasswordC string `gorm:"-"`

    // The Users FULL NAME (e.g. Burt Reynolds)
    Fullname string `gorm:"size:255; not null"`

    // The Users Karma level
    Karma int

    // Is the user banned?
    Banned bool
}

But PasswordC still shows up in my database using db.AutoMigrate(User{}) I thought gorm:"-" made it be ignored, I wanted to have a PasswordC field for using with Gorilla Schema

Source

Gacnt

Most helpful comment

Please release a new version

zbintliff on 14 Mar 2017

👍5

All 12 comments

Are you using an old version?

jinzhu on 1 May 2016

I am using the most latest version, my above struct is still creating a PasswordC field in the database:

http://imgur.com/2VxLPLa

I just deleted gorm and did a fresh go get github.com/jinzhu/gorm and I deleted the users table but it still comes back with the passwordc field

package models

import (
    "log"

    "github.com/jinzhu/gorm"
    _ "github.com/jinzhu/gorm/dialects/postgres"
)

var DB *gorm.DB

func init() {
    db, err := gorm.Open("postgres", "user=postgres dbname=bdo_pug sslmode=disable")
    if err != nil {
        log.Println(err)
    }
    DB = db

    DB.AutoMigrate(&User{})
}

Gacnt on 1 May 2016

Seemed to fix it by adding sql:"-" to it but I thought that was the responsibility of the gorm:"-" flag

Gacnt on 1 May 2016

I don't know why this issue was so quick to close. It is clearly an issue that is still an issue, unless the documentation or the code needs to figure out which one is backwards

http://stackoverflow.com/questions/36963008/gorm-not-ignoring-field-with-gorm/36974118#36974118

Gacnt on 2 May 2016

Hi @Gacnt

Sorry for this, I made a mistake, as there are some misusage about tags before caused by not upgrade to latest version, I thought this is same issue.

Just fixed this, sorry.

jinzhu on 2 May 2016

I'm having the same problems using the most recent version of gorm.

type User struct {
  gorm.Model
  Email string `json:"email" gorm:"column:email"`
  /*
  ...
  */
  UserData map[string]interface{} `json:"data" sql:"-" gorm:"-"`

sql: Scan error on column index 9: unsupported driver -> Scan pair: []uint8 -> map[string]interface{}