Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save issue #7219

Closed
hn-n opened this issue Oct 2, 2024 · 5 comments
Closed

Save issue #7219

hn-n opened this issue Oct 2, 2024 · 5 comments
Assignees
Labels

Comments

@hn-n
Copy link

hn-n commented Oct 2, 2024

Description

Unexpected behavior from Save

Code: case 1

result := Db.Save(&services[i])
if result.Error != nil {
    fmt.Println("Error:", result.Error)
    return
}

Result

results: it inserts a new record while the ID is not null.

Code: case 2

result :=Db.Save([]Services{service[i]})
if result.Error != nil {
    fmt.Println("Error:", result.Error)
    return
}

### Result

it updates, but when updating the struct as a slice, it resets the created_at of the record 0001-01-01 03:06:52+03:06:52

i'd like to help with this issue!

@github-actions github-actions bot added the type:missing reproduction steps missing reproduction steps label Oct 2, 2024
Copy link

github-actions bot commented Oct 2, 2024

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.ioSearch Before Asking

@franciscocpg
Copy link

I have the same issue.

The first call to Save, sets the created_at and updated_at, but the second call changes created_at with a null value. The second call should not add the created_at field to the update selections.

Copy link

github-actions bot commented Oct 3, 2024

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.ioSearch Before Asking

Copy link

github-actions bot commented Oct 4, 2024

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.ioSearch Before Asking

Copy link

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.ioSearch Before Asking

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants