Multi-tiered edit-inline or multi-page admin screens?

Hi, I can't seem to get edit-inline to work deeper than one level. Simplified example: class A(meta.Model): fields = ( meta.CharField('a_value'), ) admin = meta.Admin() class B(meta.Model): fields = ( meta.ForeignKey(A, edit_inline=True), meta.CharField(

Re: Foreign keys in Django models without id fields?

Another scenario not uncomon where integer ID are not the best is when 2 tables from 2 location need to be merged into one table (ex. collect data from 2 stores and maintain it centraly somewhere). There are many cases where people are working closely to the database like datawarehosing or if the

Re: Problems with User Auth stuff

I made it work with the users going in django.models.auth. But it is not a very good solution as it becomes project-wide and I cannot have another similar application. I think we need to have a way to tell the auth/sessions framework the correct user tables to use. It is hardcoded to pick the dja

Re: edit_inline

On Aug 2, 2005, at 12:17 PM, raffaele messuti wrote: class Label(meta.Model): fields = ( meta.CharField('name', 'name', maxlength=200, core=True), meta.URLField('url', 'url', blank=True, core=True), ) #admin = meta.Admin() def _

edit_inline

using this simple model: class Label(meta.Model): fields = ( meta.CharField('name', 'name', maxlength=200, core=True), meta.URLField('url', 'url', blank=True, core=True), ) #admin = meta.Admin() def __repr__(self): r

Django + Apache2 and mod_python on FreeBSD 5.4

Hi, I'm posting this in case anyone else is having trouble persuading the current FreeBSD 5.4 'port' installations of mod_python / Apache2, and Django to play together nicely. Trivial mod_python examples work fine, but attempts to run Django result in Apache crashing with: Fatal erro

Re: deployment processes

How about continuous integration using BuildBot to automatically deploy the latest checked in code onto the testing environment and run tests using doctest/py.test/Twill/Selenium/PyFIT/whatever? Regards, Mamading.

What's about 'on delete restrict' emulation?

By default, django deletes all related objects(records) What method i must overload in Model class, to protect some records from this total annihilation :) Simply i whant to raise exception - ThisObjectCanNotBeDeleted, coz it haz related, that can not be deleted at all (history).

Re: deployment processes

Just to add: testing and production environment would have either MySQL or PostgreSQL Any thoughts?