Any new infos on this one? I'd love to see it in django.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To
YUSS. Yeah, it's just been kind of frustrating trying to get this to work
lately. I designed a whole model set, then realized that it won't work with
admin :) 1.4.1?
Thanks,
- TK
On Fri, Mar 30, 2012 at 3:09 PM, ptone wrote:
>
>
> On Friday, March 30, 2012 1:58:08 PM UTC-7, Tyler Kocheran wr
On Friday, March 30, 2012 1:58:08 PM UTC-7, Tyler Kocheran wrote:
>
>
> The real point is that I shouldn't be getting errors if I want to have a
> OneToOneField inline of an Address on a Person. No matter what side the
> relation is declared on, inlines should just workâ˘. Maybe it's not the bes
I mean "multiple types of objects." Basically, in the db, it looks a bit
like this:
create table address(id int primary key auto increment, name text, address
text);
create table person(id int primary key auto increment, first_name
varchar(30),
last_name varchar(30), address_id int foreign
On Friday, March 30, 2012 11:44:29 AM UTC-7, Tyler Kocheran wrote:
There's really no reason for an `Address` to know of itself what it is
> owned by, it could be owned by multiple different objects.
>
Not if you are using a OneToOneField...
I think you are just looking for a FK to an addres
