Issue 370 -- Smarter caching of cached foreign key objects
Updated 1 year, 8 months ago
| David Pollak | Reviewers | ||
| dpp, marius, charles, heiko, joni, atsuhiko, jorge, naftoli, kris, indrajit, alexb, dlouwers, mstarzyk, rmellgren, jhoffman, probinett, jmadsen, mhartmann, jstrachan, jgoday | |||
| None | LiftWeb-archive | ||
https://liftweb.assembla.com/spaces/liftweb/tickets/370-when-setting-the-fk-of-a-mappedforeignkey-its-_obj-should-not-be-uncached-unless-its-incorrect dpp_issue_370 Smarter caching of foreign key objects
none
I would vote against 'foreign.' I think it was introduced through the evolution of LongMappedForeignMapper -> LongMappedMapper whose features are mostly folded in to MappedLongForeignKey by now. Originally it used foreign instead of obj because it introduced new semantics, but now that obj follows those semantics I see no purpose in 'foreign.'