Gorm gorm forces it's own primary key when i want to use my own

Example:

type Trigger struct {
    Base
}

type Base struct {
    ID        string    `gorm:"primaryKey;autoIncrement:false;type:uuid" json:"id"`
}

txn := db.DB.Create(&triggers)

when trigger.ID exists, and i want gorm to use it, it ends up creating a new ID regardless. This becomes hard to handle and confusing when you keep having to come back to it.

Behaviour remains the same for:

txn := db.DB.Save(&triggers)
txn := db.DB.Where(models.Base{ID: trigger.ID}).FirstOrCreate(&trigger)

How do I literally force in my own primary key for a txn?

Comment From: github-actions[bot]

The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨

Comment From: 0x0elliot

that's really not necessary. the issue itself is pretty simple. if required, i will understand how to help out properly by making the playground link.

Comment From: github-actions[bot]

Comment From: goamaral

I was not able to reproduce your problem. Because you are ID is uuid type, I assume you are using postgres or sqlite. I implemented a test to replicate your problem and was not able to. https://github.com/goamaral/playground/commits/issue-7343 https://github.com/goamaral/playground/commit/d395eee285dc68dabbf1e95d6cbffd185425f450

Comment From: github-actions[bot]