I see what you mean. I agree to an extent - data needs to stay as
clean as possible. But this isn't the goal in every situation, and
doesn't always mean that data is erroneous - it can simply be lacking.
Simplified use case:
I've got for example a table that contains foreignkeys to another
"addit
Sorry for the previous one, accidentally pressed alt-s
What I meant to say was: as far as I can see your problem is mostly covered
by faulty db-design or maintenance, which is not something django should
cover in my opinion, it seems logically you do a cleaning of your database
to set all non-exis
Hi
2009/2/21 Adys
>
> Hi there
>
> I've been thinking for the past couple of days of a simple "lazy"
> ForeignKey design (or whichever name would fit better). It's something
> I've tried really hard to find in Django, unsuccessfully. Some
> explanation first...
>
Lazy is imho not a decent name i
Hi there
I've been thinking for the past couple of days of a simple "lazy"
ForeignKey design (or whichever name would fit better). It's something
I've tried really hard to find in Django, unsuccessfully. Some
explanation first...
I tried to get some background on django-users, cf
http://groups.g
