Skip to content

No Support for ForeignKey Caches #1

Open
philipkimmey opened this Issue Jul 5, 2011 · 1 comment

2 participants

@philipkimmey

Hi there!

Great work on this project. It looks like the commits have been coming fast recently, and I realize you say support for ForeignKey fields is planned, but I just wanted to put a ticket in to ping you about that.

ForeignKey support would be a great feature and would significantly decrease db hits for me.

The scaling isn't that important for me yet, so I probably won't be able to commit any time to helping out with this feature in the immediate future, but once we go live if this is a bottleneck I'd certainly be happy to work on this.

Thanks!

@lamby lamby added a commit that closed this issue Jul 8, 2011
@lamby lamby Blindly set instance._state.db to fix ForeignKey/m2m issues. Closes GH-1
.

Signed-off-by: Chris Lamb <chris@playfire.com>
a0f51e2
@lamby lamby closed this in a0f51e2 Jul 8, 2011
@lamby lamby reopened this Jul 8, 2011
@lamby
lamby commented Jul 8, 2011

Closed wrong issue, apologies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.