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

*pq.Error: update or delete on table "calendars" violates foreign key constraint "parent_calendar" on table ... #6

Open
TetAlius opened this issue Jun 2, 2018 · 1 comment
Assignees
Labels
bug v0.1.4 issues that will be fix on release v0.1.4

Comments

@TetAlius
Copy link
Owner

TetAlius commented Jun 2, 2018

https://sentry.io/gosyncmycalendars/gosyncmycalendars/issues/569938402/

*pq.Error: update or delete on table "calendars" violates foreign key constraint "parent_calendar" on table "calendars"
  File "github.com/TetAlius/GoSyncMyCalendars/frontend/db/calendar.go", line 76, in deleteFromUser
    data.sentry.CaptureError(err, map[string]string{"database": "frontend"})
  File "github.com/TetAlius/GoSyncMyCalendars/frontend/db/user.go", line 190, in DeleteCalendar
    return data.deleteFromUser(calendar, user)
  File "github.com/TetAlius/GoSyncMyCalendars/frontend/frontend.go", line 281, in calendarHandler
    err := s.database.DeleteCalendar(currentUser, id)
  File "github.com/TetAlius/GoSyncMyCalendars/frontend/frontend.go", line 93, in calendarHandler)-fm
    mux.HandleFunc("/calendars/", server.calendarHandler)
  File "net/http/server.go", line 1947, in ServeHTTP
    f(w, r)
...
(9 additional frame(s) were not displayed)

pq: update or delete on table "calendars" violates foreign key constraint "parent_calendar" on table "calendars"

Button of remove calendar should be disable when a link between the calendar exists

@TetAlius TetAlius self-assigned this Jun 2, 2018
@TetAlius TetAlius added bug v0.1.2 issues that will be fix on release v0.1.2 labels Jun 2, 2018
@TetAlius
Copy link
Owner Author

TetAlius commented Jun 8, 2018

This is moved to next release, and will continue to moved if some other critical changes must be done

@TetAlius TetAlius added v0.1.3 issues that will be fix on release v0.1.3 v0.1.4 issues that will be fix on release v0.1.4 and removed v0.1.2 issues that will be fix on release v0.1.2 v0.1.3 issues that will be fix on release v0.1.3 labels Jun 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug v0.1.4 issues that will be fix on release v0.1.4
Projects
None yet
Development

No branches or pull requests

1 participant