On 4/22/06, nevroe <[EMAIL PROTECTED]> wrote:
>
> ManyToMany("self") isn't a supported feature of Django (yet),
...erm... yes it is (at least, in magic removal, which you seem to be
using). Look for the m2m_recursive model test in the Django
distribution.
If this isn't working for you, then you
I think I got it.
Basically, my old file structure looked like this:
wiki (directory)
__init.py__
views.py
models (directory)
__init__.py
wiki.py
What I did was move wiki.py into the wiki folder and rename it
models.py. Then I deleted the models folder. So the final result
When I define a model:
>>> class Test(models.Model):
>>> ... some other fields ...
>>>bool_field = models.BooleanField(default=True)
Django generate next sql:
CREATE TABLE `test_test` (
`id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
... some other fields ...
> admin.logentry: 'user' has relation with uninstalled model User
>admin.logentry: 'content_type' has relation with uninstalled model
> ContentType
I would guess you need "UPDATE" statements for the content_types table.
You should be able to see what those are (and they will vary for
On 04/23/06 00:15, Richie Hindle wrote:
> Hi,
>
> I'm porting my app from the trunk to Magic Removal. I've carried out all
> the steps at http://code.djangoproject.com/wiki/RemovingTheMagic but I'm
> having various problems - I imagine they're all linked to some mistake
> I've made somewhere
Wow! I was just upgrading an app and came up with these three
questions myself. Any help would be appriciated. This seems to be a
porting issue, as I am not having problems 1 & 2 with the new site I am
working on.
--~--~-~--~~~---~--~~
You received this
Hi,
I'm porting my app from the trunk to Magic Removal. I've carried out all
the steps at http://code.djangoproject.com/wiki/RemovingTheMagic but I'm
having various problems - I imagine they're all linked to some mistake
I've made somewhere along the line:
o When I run "manage.py runserver" I
Hi Berry,
Beegee wrote:
> My test results. I installed
> mysql-standard-5.0.20-linux-x86_64-glibc23. Created a completely new
> database and restored a backup from my 'old' django database into the
> newly created MySql 5 instance.
>
> Restarted Apache and everthing was up and running again.
I had *many* problems with Django on Dreamhost the first two weeks
that my systems ran there. Suddenly there are no more... I don't know
what they did, what I did, or anything else.
There's a page on the Dreamhost panel for you to vote on new
features that they should add. Maybe +1 on an
Graham King wrote:
> In the RemovingTheMagic wiki page, the MySQL for upgrading the database
> has these two lines:
>
> ALTER TABLE django_content_type rename package to app_label;
> ALTER TABLE django_content_type rename python_module_name to model;
>
> In MySQL 4.1.14 (and in the
Beegee wrote:
> Currently I am using MySQL version 4.0.24. Looking at all the answers
> the best thing to do is to try MySQL v5. I will do some testing over
> the weekend and post my experiences.
>
> Thanks very much for your help.
Just FYI, binary upgrading 4.0 to 5.0 is a bad idea: dump data
On Fri, 21 Apr 2006 08:35:44 -0700
"arthur debert" <[EMAIL PROTECTED]> wrote:
>
> Oh My!
>
> my bad. yes that should read..
> " are not going to achieve *great* performance on DREAMHOST."
>
> I just meant to say that dreamhost has nice price / feature ration but
> it's just a little
ManyToMany("self") isn't a supported feature of Django (yet), so many
people suggested to me that I can get around it by making an
intermediary model class, which has two foreign keys to the model I'm
interested in. Here's what an example scenario looks like:
class Node(models.Model):
path
I was playing with a small app the other day (in m-r) & had trouble with
one of my models showing up in the admin interface. After much scratching
of my head, I found the I had written -
supplier = models.ManytoManyField(Supplier)
The uncapitalized "to" caused it not to work but there were no
On Saturday 22 April 2006 04:08, C. Allwardt wrote:
> You were correct in the "guessing" at what I meant :-) It would have
> been more precise to state 0-1 to many. In either case I tried the
> blank=True method and it seemed to get me a runtime error. Then
> again it was late in the day and
Hi,
As a newbie I have been working through the Django Tutorial. I must say
it is very well written, even so I have hit a wall...
I have activated the admin site, and created a superuser and can log in
as the superuser.
What I have sofar failed to do is to add the demo site (polls) to the
admin
In the RemovingTheMagic wiki page, the MySQL for upgrading the database
has these two lines:
ALTER TABLE django_content_type rename package to app_label;
ALTER TABLE django_content_type rename python_module_name to model;
In MySQL 4.1.14 (and in the docs for MySQL 5.0), the commands
On Apr 21, 2006, at 10:24 PM, Mathieu Blondel wrote:Hi all,Maybe I'm missing something but I can't find how to specify the numberof objects (lines) per page in the admin.The default is 100 which is too much for me.Thanks,In 0.91, you need to edit DEFAULT_RESULTS_PER_PAGE in
18 matches
Mail list logo
