I just installed 1.0.2 final and the bug has been fixed in that.
-- Peter
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To un
On Tue, Dec 30, 2008 at 2:37 PM, Peter wrote:
> > (You don't say what version of Django you are using.)
>
> Sorry - 1.0 final
>
> > What you describe
> > sounds similar to a few problems that have been reported.
>
> Ah yes. I looked. Thanks. Nasty.
>
> > but I believe the only way to
> > complete
> (You don't say what version of Django you are using.)
Sorry - 1.0 final
> What you describe
> sounds similar to a few problems that have been reported.
Ah yes. I looked. Thanks. Nasty.
> but I believe the only way to
> completely ensure you do not see this issue with PostgreSQL at present i
Thank you Ana, I checked that out - but I don't understand how it
works (at least not without looking at the
other models).
Is Django less solid with Django than MySQL? I mean my example is a
trivial 'text book' example
and it did not work with PostgreSQL
-- Peter
On Dec 30, 6:49 pm, Ana wrot
Hello Peter,
I use Postgres and have success creating a manytomany table. See:
http://dpaste.com/103824/
Ana
On Dec 30, 10:29 am, Peter wrote:
> I have two models: Person and Telephone. A person can have many
> telephones but a telephone belongs to at most one person. The models
> are:
>
> c
On Tue, Dec 30, 2008 at 1:29 PM, Peter wrote:
>
> I have two models: Person and Telephone. A person can have many
> telephones but a telephone belongs to at most one person. The models
> are:
>
> [snipped]
> Using PostgreSQL this allows me a single phone number for a person. I
> can chnage and de
6 matches
Mail list logo
