Home  >  Article  >  Backend Development  >  Gorm preloading gives ambiguous column error

Gorm preloading gives ambiguous column error

王林
王林forward
2024-02-10 19:12:07566browse

Gorm 预加载给出了不明确的列错误

php editor Zimo introduces to you the ambiguous column error in Gorm preloading. Gorm is an ORM library commonly used in Go language for implementing database operations. When using Gorm for preloading, you sometimes encounter ambiguous column errors. The reason for this error may be that the database table structure is inconsistent with the Gorm model definition, or the preloaded association table column name is incorrect. The solution to this problem is to check the database table structure and Gorm model definition to ensure that they are consistent, and double-check that the preloaded association table column names are correct. By solving this error, you can successfully use Gorm for preloading operations and improve database operation efficiency.

Question content

I have the following structure

type employee struct {
    employeeid        int64  `gorm:"primary_key;column:employee_id"`
    employeecode      string `gorm:"column:employee_code"`
    firstname         string `gorm:"column:first_name"`
    lastname          string `gorm:"column:last_name"`
    designationid     int64  `gorm:"column:designation_id;"`
    designation       *designation `gorm:"foreignkey:designationid"`
}

type designation struct {
    designationid   int64  `gorm:"primary_key;column:designation_id"`
    designationname string `gorm:"column:designation_name"`
}

func getemployee(id int64) (*employee, error) {
    db := connection.getconn() //get connection
    defer db.close()

    employee := &employee{}
    err := db.model(employees).preload("designation", func(db *gorm.db) *gorm.db {
        return db.join("inner join employees on employees.designation_id = designations.id").order("employees.first_name desc")
    }).find(employee).error
    return employee, err
}

The generated query is

SELECT * FROM employees;
SELECT * FROM designations INNER JOIN employees ON employees.designation_id = designations.id WHERE id IN (1,2) order by employees.first_name DESC;

I have a connection similar to what I wrote in the function above. Here I am not able to connect correctly, but in real case I know I need to connect and there is id field in both preload table and join table. Since both tables have same column name i.e. id in this case mysql will throw error

Error 1052: Column "id" in where clause is ambiguous

I encountered this problem in gorm v1.9.16

I didn't find any resources that mentioned similar issues. How do we solve this problem?

Workaround

Can you try using the latest version (> v1.20.x)?

This issue has been closedhttps://github.com/go-gorm/ gorm/issue/2653

This problem seems to be solved in the new versionhttps://github.com/go-gorm/gorm/commit/2ae0653af2bc19cd31f687e797b189c85f0ac3f6

The above is the detailed content of Gorm preloading gives ambiguous column error. For more information, please follow other related articles on the PHP Chinese website!

Statement:
This article is reproduced at:stackoverflow.com. If there is any infringement, please contact admin@php.cn delete