Skip to content

Conversation

jmattheis
Copy link
Member

sqlite3 doesn't support adding a foreign key via gorm.DB#AddForeignKey
this would mean, that we have some hacky solutions for having foreign
keys for sqlite and the other databases. Therefore manually deleting
the referencing models seems to be the best solution. We already have
interfaces for database capsuling, so no api must be adjusted.

sqlite3 doesn't support adding a foreign key via gorm.DB#AddForeignKey
this would mean, that we have some hacky solutions for having foreign
keys for sqlite and the other databases. Therefore manually deleting
the referencing models seems to be the best solution. We already have
interfaces for database capsuling, so no api must be adjusted.
@jmattheis jmattheis requested a review from nicories April 1, 2018 09:28
@codecov
Copy link

codecov bot commented Apr 1, 2018

Codecov Report

Merging #40 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master    #40   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          24     24           
  Lines         671    676    +5     
=====================================
+ Hits          671    676    +5
Impacted Files Coverage Δ
database/application.go 100% <100%> (ø) ⬆️
database/user.go 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c1444da...d533a5f. Read the comment docs.

@jmattheis jmattheis merged commit c912bb8 into master Apr 1, 2018
@jmattheis jmattheis deleted the db-delete branch April 1, 2018 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants