From fb9da5ec8d58e6ba888ca0922602e8fec137794d Mon Sep 17 00:00:00 2001 From: blitzmann Date: Sat, 3 May 2014 00:40:13 -0400 Subject: [PATCH] Revert "Create new Fit relationship with fits that current fit is projected onto (see #90)" This reverts commit a2727d5f4750a3f4fff785100fe0ec8eafabf220. --- eos/db/saveddata/fit.py | 7 ------- 1 file changed, 7 deletions(-) diff --git a/eos/db/saveddata/fit.py b/eos/db/saveddata/fit.py index 16dd17f6a..25516b7b6 100755 --- a/eos/db/saveddata/fit.py +++ b/eos/db/saveddata/fit.py @@ -65,12 +65,5 @@ mapper(Fit, fits_table, primaryjoin = projectedFits_table.c.victimID == fits_table.c.ID, secondaryjoin = fits_table.c.ID == projectedFits_table.c.sourceID, secondary = projectedFits_table, - collection_class = HandledProjectedFitList), - # projectedOnto is not currently used and probably won't be - # It simply makes data clean-up easier. See GH issue #90 - "_Fit__projectedOnto" : relation(Fit, - primaryjoin = fits_table.c.ID == projectedFits_table.c.sourceID, - secondaryjoin = fits_table.c.ID == projectedFits_table.c.victimID == fits_table.c.ID, - secondary = projectedFits_table, collection_class = HandledProjectedFitList) })