On Mon, 2006-10-09 at 05:31 -0700, Panos Laganakos wrote:
> > There are a few corner cases for objects that only have an implicit
> > primary key field like this. Working with them in the admin interface is
> > one of the areas that may or may not work. It's not really worth us
> > putting in an
> There are a few corner cases for objects that only have an implicit
> primary key field like this. Working with them in the admin interface is
> one of the areas that may or may not work. It's not really worth us
> putting in an enormous amount of time to get all of this ironed out,
> since you
Malcom, I hear what you're saying.
But regarding this particular project, its just the way I would have
done it if I wrote it directly to SQL.
One table for the DVDs and one table for the Files, etc.
I need to be able to manipulate it from the admin, so I can handle the
DVD objects explicitly.
On Sun, 2006-10-08 at 14:52 -0700, Panos Laganakos wrote:
> > Try using the same pattern you' ve used with the Dvd class with the
> > inner Admin class,
> > like this:
> >
> > class Dvd(models.Model):
> > pass
> >
> > class Admin:
> > pass
> >
> > That should solve both
> Try using the same pattern you' ve used with the Dvd class with the
> inner Admin class,
> like this:
>
> class Dvd(models.Model):
> pass
>
> class Admin:
> pass
>
> That should solve both problems (that really are of the same issue, when
> an admin view has been
Panos,
On 10/8/06, Panos Laganakos <[EMAIL PROTECTED]> wrote:
>
> What I'm doing is this:
>
> class Dvd(models.Model):
> pass
>
>
> class File(models.Model):
> #...
> dvd = models.ForeignKey('Dvd', blank=True, null=True)
>
> [...]
>
> Problem is, I'm not sure how to define something
What I'm doing is this:
class Dvd(models.Model):
pass
class File(models.Model):
#...
dvd = models.ForeignKey('Dvd', blank=True, null=True)
I'm using blank and null, 'cause the file might not be backed up to a
DVD yet.
Problem is, I'm not sure how to define something to 'class
7 matches
Mail list logo
