I know Jacob was working on this, is it still going ahead as planned?
I don't see a wiki, and I'd like to work on it.
Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to th
Strange, for me it works like said in 1). After the new object is
saved, the id field is not None, but the true id of the object in
database. Maybe I did not understand something?
Also, if you look at the tutorial at
http://www.djangoproject.com/documentation/tutorial1/ it says:
# No polls are
On Wed, 2006-04-19 at 09:10 +, favo wrote:
> on this section:
> http://code.djangoproject.com/wiki/RemovingTheMagic#Databasechangesyoullneedtomake
>
> for postgresql part,
>
> 1)correct:
> ALTER TABLE django_content_type DROP CONSTRAINT "$1";
> should be -->
> ALTER TABLE django_content_type
and there's also some index with wrong name, which is not really a
problem.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegro
on this section:
http://code.djangoproject.com/wiki/RemovingTheMagic#Databasechangesyoullneedtomake
for postgresql part,
1)correct:
ALTER TABLE django_content_type DROP CONSTRAINT "$1";
should be -->
ALTER TABLE django_content_type DROP CONSTRAINT
"content_types_package_fkey";
2) lack :
ALTER T
Just a quick note from someone who has been trying to get his head
around Dojo - this is really appreciated James!
Cheers,
Tone
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
In the absence of any objections then, I'll add it in, in the location
Max suggested.
Luke
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-deve
