Re: Model inheritance with optional self reference

Just facing the same problem with you bro, and i ended up with proxy model and using django-treebeard for the data hierarchy... On Thu, 11 Mar 2021 at 17.47 Kunal Solanke wrote: > Btw parts should be a m2m field ig. > > On Thu, Mar 11, 2021, 16:14 Kunal Solanke > wrote: > >> That's too hard

Re: Model inheritance with optional self reference

Btw parts should be a m2m field ig. On Thu, Mar 11, 2021, 16:14 Kunal Solanke wrote: > That's too hard of a problem statement for me,ig more experienced people > will be able to answer it more properly. But if its 99.99% I'd go with > whatever you have right now, rather than creating bunch or

Re: Model inheritance with optional self reference

That's too hard of a problem statement for me,ig more experienced people will be able to answer it more properly. But if its 99.99% I'd go with whatever you have right now, rather than creating bunch or proxy models. On Thu, Mar 11, 2021, 16:06 Mateusz Wroblewski wrote: > Hi All, > > does

Model inheritance with optional self reference

Hi All, does anybody have experience with the following data model and could advise which Django tools fit it best? Background: I have two types of Components (Core and Complex) that share many attributes and methods, but also have their own, specific data fields and methods. What

Re: Model Inheritance across apps

On 30/09/2016 10:33 AM, Malik Rumi wrote: Assume two models, class Parent(models.Model): and Child(Parent): Assume they are both in the same Project Can Child be in a different app than Parent? In most cases the answer seems to be yes. True. You only need to import Parent. But it might be

Model Inheritance across apps

Assume two models, class Parent(models.Model): and Child(Parent): Assume they are both in the same Project Can Child be in a different app than Parent? In most cases the answer seems to be yes. Each app has many other models to which Parent and Child, respectively, are closely tied - which is

Queries regarding Custom Managers with model inheritance.

I was going through https://docs.djangoproject.com/en/1.9/topics/db/managers/#custom-managers-and-model-inheritance regarding custom managers and I decided to do some tests. Here are my models: from django.db import models class CustomManager(models.Manager): use_for_related_fields

Re: Model inheritance with constraints

On Wed, Jun 1, 2016 at 12:45 PM, Arnab Banerji wrote: > Nevermind my last comment on this thread, when I refactored my existing > model into an abstract base class with overrides, and then ran > "makemigrations", Django said "no changed detected", so it is merely > treated as

Re: Model inheritance with constraints

Nevermind my last comment on this thread, when I refactored my existing model into an abstract base class with overrides, and then ran "makemigrations", Django said "no changed detected", so it is merely treated as a code refactor and not a database related change. Thanks AB -- You received

Re: Model inheritance with constraints

Hi Akhil - my issue was how to avoid the new OneToOne relationships, which James addressed on this post. Hi James - thanks a bunch for your help, much appreciated. While I like the WYSIWYG nature of this solution, I am not sure if the creation of the abstract base class will cause the data

Re: Model inheritance with constraints

*only* _myanotherfunmodel table with > fields "my_foo_field" and "my_another_foo_field", *without* touching any > data in the _myfunmodel table. > > None of the options in > https://docs.djangoproject.com/en/dev/topics/db/models/#model-inheritance > seem to addre

Re: Model inheritance with constraints

FunModel(MyFunModel): > my_another_foo_field = > > Such that the migration gives me *only* _myanotherfunmodel table with > fields "my_foo_field" and "my_another_foo_field", *without* touching any > data in the _myfunmodel table. > > None of the option

Model inheritance with constraints

ct.com/en/dev/topics/db/models/#model-inheritance seem to address this case, or maybe I am missing something? Thanks, AB -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it,

Re: proxy model inheritance generates a migration file in a third party app

Hi Markus, Thank you very much, that solved the issue. Many thanks, Iliana On Thursday, 28 January 2016 17:31:36 UTC-7, Markus Holtermann wrote: > > Hello Iliana, > > this is due to the definition of app_label = 'actstream' on your proxy > model. This tells Django that this model should

Re: proxy model inheritance generates a migration file in a third party app

Hello Iliana, this is due to the definition of app_label = 'actstream' on your proxy model. This tells Django that this model should belong to another app. Hence the migrations involving that model are added to the actstream app's migrations. /Markus On Friday, January 29, 2016 at 10:14:24

proxy model inheritance generates a migration file in a third party app

Hello, I am using a third party app actstream (https://github.com/justquick/django-activity-stream) and am creating a proxy for one of the original actstream models : # myapp/models.py from actstream.models import Action # Subclass

Re: Django model inheritance: create sub-instance of existing instance (downcast)?

;>>> Sample Use-case- >>>> >>>> When the system is first deployed, a restaurant instance is created. >>>> Later, the restaurant adds a bar to increase revenue, and we now want to >>>> create a Bar model instance for the parent Place for the r

Re: Django model inheritance: create sub-instance of existing instance (downcast)?

Place = Restaurant.objects.get(name__iexact="Bob's Place").parent >>> barInstance = Bar(parent=parentPlace, happy_hour=True) >>> >>> However, if you attempt to create an instance in this manner now, you >>> receive a DatabaseIntegrityError, say

Re: Django model inheritance: create sub-instance of existing instance (downcast)?

entPlace, happy_hour=True) >> >> However, if you attempt to create an instance in this manner now, you >> receive a DatabaseIntegrityError, saying that a Place object with that id >> already exists. >> >> }}} >> >> How to get this solved? >> >> There are wo

Re: Django model inheritance: create sub-instance of existing instance (downcast)?

e = Restaurant.objects.get(name__iexact="Bob's Place").parent > barInstance = Bar(parent=parentPlace, happy_hour=True) > > However, if you attempt to create an instance in this manner now, you > receive a DatabaseIntegrityError, saying that a Place object with that id > alrea

Django model inheritance: create sub-instance of existing instance (downcast)?

ue) However, if you attempt to create an instance in this manner now, you receive a DatabaseIntegrityError, saying that a Place object with that id already exists. }}} How to get this solved? There are work arounds: http://stackoverflow.com/questions/4064808/django-model-inheritance-create-sub-

Re: OneToOne field versus model inheritance

Hi, Django doesn't really provide a way to create a subclass from an already existing object in the admin. It's actually pretty hard to do even in the code. So for that reason I'd recommend the non subclass with the OneToOneField. Actually, if I were doing it, this is what I would do: class

OneToOne field versus model inheritance

I have three models: Person, Client, Member Person is a base model, Client and Member are profiles for Person. class Person(AbstractBaseUser, PermissionsMixin): email = models.EmailField( verbose_name=_('email address'), max_length=255, unique=True, ) class

Re: Possible Model Inheritance Issue? Error: [Model_Name] instance needs to have a primary key value before a many-to-many relationship can be used

I know this is a VERY VERY old thread but oh my god I love you, I was having the same problem for the same reason and would have never imaged that was why (though it makes sense). Took me a long time to finally find this thread. On Thursday, January 22, 2009 1:38:57 AM UTC-2, Keyton Weissinger

True Model Inheritance

I know that there are several model inheritance extensions available: https://www.djangopackages.com/grids/g/model-inheritance/ But it is hard for me to decide which one to take. The most common solutions seem to be: django-model-utils django-polymorphic My use case is simple

Re: db performance with model inheritance vs. alternatives

Hello @all, just to be clear and honest upfront: I've just posted this question on http://stackoverflow.com/questions/20373194/db-performance-with-model-inheritance-vs-alternatives as well. I hope this is okay and doesn't upset anyone. Thanks again. So long, Matthias -- Dipl.-Inf. (FH

db performance with model inheritance vs. alternatives

jumps to mind is model inheritance for the plugins. But since it is unforeseeable how many plugins an installation will have and how many a specific model instance will have attached to it or what kind of plugins (since the plugin system is heterogenous), performance is a great concern of mine. Each

Re: model inheritance

Is there maybe a way to set the cmsplugin_news.News.Meta.abstract option to True? In order to prevent accessing the parent model to fetch the inherited data. On 10/02/2013 03:45 PM, Leonardo Giordani wrote: > Are you sure your DB has been synced after putting the > ForeignKey(News) in your

Re: model inheritance

Hi Leonardo, thanks for your answer. Yes, it has been synced. The model itself is a little bit bigger, as you can notice from the code https://dpaste.de/c3Rg I am using as well the News model from https://github.com/wildfish/cmsplugin_news/blob/master/cmsplugin_news/models.py Regards, Roberto

Re: model inheritance

Are you sure your DB has been synced after putting the ForeignKey(News) in your Department model? Can you post somewhere the following models: News, OldNews, Department? Regards, Leo Leonardo Giordani Author of The Digital Cat My profile on About.me

model inheritance

Hi, I am extending a 3rd party model in my application, using multi-table inheritance. I can create an instance and modify it, but when I try to list the created objects at http://localhost:8000/en/admin/news/news/ , I am getting a nice exception: Traceback: File

Re: Model inheritance problem

Ah okay, well I've never used that, I thought you were implying this could be a general Django question. Maybe neo4django doesn't support model inheritance -- I took a look at their site briefly and couldn't see anything about it. Sorry not to be more help... On Tuesday, 17 September 2013 15

Re: Model inheritance problem

Hmm, no, it does not work even without indexed=True, my mistake. So the "issue" remains. Il giorno martedì 17 settembre 2013 16:17:04 UTC+2, Antonio Mignolli ha scritto: > > Thanks, George, but as I said in the beginning, I'm using neo4django, > which surely has StringProperty, otherwise I

Re: Model inheritance problem

Thanks, George, but as I said in the beginning, I'm using neo4django, which surely has StringProperty, otherwise I would have an AttributeError on StringProperty, which I don't have. I should have written: from neo4django.db import models and ... name = models.StringProperty(indexed=True)

Re: Model inheritance problem

> class MyBaseModel(models.NodeModel): >name=StringProperty() >class Meta: >abstract = True > > In Django you would need CharField or similar. StringProperty is a Google App Engine thing? Cf

Model inheritance problem

Hi, I posted something similar also to italian Django-it group. I'm using neo4django, but I want to understand things in a more generic way. My case: class MyBaseModel(models.NodeModel): name=StringProperty() class Meta: abstract = True NodeModel it's a graph Node, like a record

Re: Model inheritance, implicit OneToOneField and stray inherited reverse relations

Hi Tom, On Wednesday, June 12, 2013 10:25:24 AM UTC+2, Tomáš Ehrlich wrote: > > Hi Benjamin, > you can create explicit OneToOne field with parent_link=True > > https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.OneToOneField.parent_link > > > Then you can set different

Re: Model inheritance, implicit OneToOneField and stray inherited reverse relations

) Benjamin Wohlwend <piquad...@gmail.com> napsal(a): > Hi, > > I have a bit of a problem with inherited reverse relations and django model > inheritance. Consider these models: > > > class Content(models.Model): > display = models.BooleanField() > &g

Model inheritance, implicit OneToOneField and stray inherited reverse relations

Hi, I have a bit of a problem with inherited reverse relations and django model inheritance. Consider these models: class Content(models.Model): display = models.BooleanField() class Link(Content): url = models.URLField() class Teaser(Content): text = models.TextField

Re: Multiple model inheritance

yes, yes, no and yes. Abstract models should inherit form models.Model. Abstract models should always have a Meta class with abstract=True. The order matters when it comes to shared functionality. Here's how I would code those models you had: class Taggable(models.Model): tag =

Re: Multiple model inheritance

I’m not sure that’s possible. Even abstract Models do magic in the background. Specifically there's the _meta class attribute that gets inherited. If you were to try it, only one of the _metas would be included. On Dec 31, 2012, at 6:12 AM, Mattias Linnap wrote: > Hi all, > > I would like to

Multiple model inheritance

Hi all, I would like to define multiple abstract base models with small set of fields each. The "real" models inherit from multiple mixins to add the fields. For example: class Taggable(?): tag = models.CharField() class Visible(?): visible = models.BooleanField() class SomeFullModel(?,

django-typed-models - sane single-table model inheritance

In May last year I posted this topic<https://groups.google.com/d/topic/django-developers/1LA98LjNz-g/discussion>on django-developers. We wanted a way to do proxy-model inheritance, while preserving the type of each object when it goes in and out of the database. Unable to find an

Re: Model Inheritance Downcasting

Hallöchen! Bastian Kuberek writes: > [...] > > What I need is to be able to query the Widget class and get back > subclasses based on their type: > widgets = Widget.objects.all() print widgets > [ 5>,] We do this very reliably with http://djangosnippets.org/snippets/2091/ but I

Re: Model Inheritance Downcasting

On Wed, Nov 16, 2011 at 4:43 PM, Bastian Kuberek wrote: > Hi, > I have looked a lot and have not yet figured out how to accomplish this. > Let me show with an example what I am trying to accomplish. > > http://code.google.com/p/django-polymorphic-models/ Cheers Tom --

Model Inheritance Downcasting

Hi, I have looked a lot and have not yet figured out how to accomplish this. Let me show with an example what I am trying to accomplish. class WidgetType(models.Model): """WidgetType categorizes the type of Widget""" name = models.CharField(max_length=255) slug =

Re: Model Inheritance and ModelForms

Tom, Thanks for the quick reply! However, when I tried that I got an error saying that inventoryitem "is an invalid keyword argument for this function". I fixed this by manually specifying the OneToOneField relationship with the parent class as inventoryItem and setting parent_link=True. With

Re: Model Inheritance and ModelForms

On Fri, Oct 28, 2011 at 7:50 AM, Alex wrote: > I've been scouring Google and the Django documentation and I can't > figure out how to do this. I'm working on an inventory management > system for my shop. My inventory models.py similar to the following: > >    class ItemType(

Model Inheritance and ModelForms

I've been scouring Google and the Django documentation and I can't figure out how to do this. I'm working on an inventory management system for my shop. My inventory models.py similar to the following: class ItemType( models.Model ): def __unicode__( self ): return "blah

Model Inheritance and methods

I have the following models: class Deal(models.Model): """ Deal is a deal for Interest. There should only be one deal for each Interest pair """ interest = models.ForeignKey( Interest ) max_sell = models.IntegerField(default = 1) def terms(self):

Re: What are the advantages of Model inheritance?

On Jun 23, 11:40 pm, Micky Hulse <rgmi...@gmail.com> wrote: > On Thu, Jun 23, 2011 at 2:17 PM, bruno desthuilliers > > <bruno.desthuilli...@gmail.com> wrote: > > FWIW, I have been using model inheritance - abstract and concrete - in > > half a dozen projects, with

Re: What are the advantages of Model inheritance?

il.com> wrote: > Even ignoring the select_related then - the fact is that > > user.post_set works and user.betterpost_set won't work, seemingly as > the result of using model inheritance. > > Perhaps I could get all of the posts (post and betterposts) and then > filter by time?

Re: What are the advantages of Model inheritance?

Even ignoring the select_related then - the fact is that user.post_set works and user.betterpost_set won't work, seemingly as the result of using model inheritance. Perhaps I could get all of the posts (post and betterposts) and then filter by time? Does that make sense / is there a way to do

Re: What are the advantages of Model inheritance?

On Thu, Jun 23, 2011 at 2:17 PM, bruno desthuilliers <bruno.desthuilli...@gmail.com> wrote: > FWIW, I have been using model inheritance - abstract and concrete - in > half a dozen projects, with about 30 model subclasses in one of them, > and it JustWorks(tm). That sounds pret

Re: What are the advantages of Model inheritance?

On Jun 23, 8:24 pm, Rich Jones <miser...@gmail.com> wrote: > Other than the convenience of writing them, I can't seem to find any > advantages of using model inheritance. Really ??? > Please allow me to explain the trouble I am having with an example. > Suppose, > >

Re: What are the advantages of Model inheritance?

nvalid code (i.e. you need to add a proxy _meta??). > > My apologies if I'm wrong though, as I have never encountered a need to > do this before, and just going off vague memory. > > Cal > > On 23/06/2011 19:24, Rich Jones wrote:Other than the convenience of > writing them, I can't se

Re: What are the advantages of Model inheritance?

19:24, Rich Jones wrote:Other than the convenience of writing > them, I can't seem to find any advantages of using model inheritance. Please > allow me to explain the trouble I am having with an example. Suppose, class > Post(models.Model): title = models.CharField(max_length=200) user_owner_id =

Re: What are the advantages of Model inheritance?

On 23/06/2011 19:24, Rich Jones wrote: Other than the convenience of writing them, I can't seem to find any advantages of using model inheritance. Please allow me to explain the trouble I am having with an example. Suppose, class Post(models.Model): title = models.CharField

What are the advantages of Model inheritance?

Other than the convenience of writing them, I can't seem to find any advantages of using model inheritance. Please allow me to explain the trouble I am having with an example. Suppose, class Post(models.Model): title = models.CharField(max_length=200) user_owner_id = models.ForeignKey

Re: Abstract Model Inheritance and Custom Managers?

On Thu, Jan 13, 2011 at 9:10 PM, ringemup <ringe...@gmail.com> wrote: > If a manager is defined on an abstract model, do non-abstract child > models inherit the manager? http://docs.djangoproject.com/en/dev/topics/db/managers/#custom-managers-and-model-inheritance -- Marc --

Abstract Model Inheritance and Custom Managers?

If a manager is defined on an abstract model, do non-abstract child models inherit the manager? -- 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 unsubscribe from this group,

Re: problems with model inheritance if base class is not abstract

Mmm yes it seems you are right. But I think this is a bit confusing thinking about object oriented programming, it is not? Then the only way to avoid this seems to be use an abstract base class or use some not so clean way to simulate this behavior. On 21 Nov, 01:36, Ramiro Morales

Re: problems with model inheritance if base class is not abstract

Ramiro - you made my day. Somehow I missed this little tid bit in the docs - what a super handy feature!! thank you. On Nov 20, 4:36 pm, Ramiro Morales wrote: > On Sat, Nov 20, 2010 at 7:59 AM, marco.ferrag...@gmail.com > > > > wrote: > > Hi all!

Re: problems with model inheritance if base class is not abstract

On Sat, Nov 20, 2010 at 7:59 AM, marco.ferrag...@gmail.com wrote: > Hi all! I'm new to django and I'm experimenting with models but I have > some trouble. I've minimized my problem to this code: > > class TestBase(models.Model): >    base =

Re: problems with model inheritance if base class is not abstract

--- On Sat, 11/20/10, marco.ferrag...@gmail.com <marco.ferrag...@gmail.com> wrote: From: marco.ferrag...@gmail.com <marco.ferrag...@gmail.com> Subject: problems with model inheritance if base class is not abstract To: "Django users" <django-users@googlegroups.com>

problems with model inheritance if base class is not abstract

Hi all! I'm new to django and I'm experimenting with models but I have some trouble. I've minimized my problem to this code: class TestBase(models.Model): base = models.CharField(max_length=255) from django.contrib import admin class TestA(TestBase): testb =

Re: Model Inheritance.

Hi Tom, You might want to have a look at inheritanceCastModel from django-model-utils by Carl Meyer http://github.com/carljm/django-model-utils Best regards, Miguel Araujo 2010/10/29 David De La Harpe Golden > On 29/10/10 00:04, Tom Eastman wrote: > > That's

Re: Model Inheritance.

On 29/10/10 00:04, Tom Eastman wrote: That's correct, but I want to take a 'Place' object, that doesn't have a 'restaurant', and turn it *in to* a 'Restaurant' by adding the corresponding row to the Restaurant table. So you have a place. p = Place(name="3rd Circle of Hell") p.save() This

Re: Model Inheritance.

On 29/10/10 11:06, Carles Barrobés wrote: Your "place" object will contain an attribute called "restaurant" to access the object as an instance of the subclass. If this place object is an instance of another place subclass, accessing the restaurant attribute will raise a DoesNotExist error.

Re: Model Inheritance.

, 01:39, Tom Eastman <tom.east...@otago.ac.nz> wrote: > I'm working with model inheritance, and I need to convert my objects > into instances of its subclass.  Is there an easy way to do this? > > Looking at the example in: > > >http://docs.djangoproject.com/en/1.2/topics/db/mod

Model Inheritance.

I'm working with model inheritance, and I need to convert my objects into instances of its subclass. Is there an easy way to do this? Looking at the example in: http://docs.djangoproject.com/en/1.2/topics/db/models/#multi-table-inheritance I have a whole bunch of 'Place' objects

Re: Bug in model inheritance?

Alec, Thanks.. yeah, your fix forces the fields to pk=True, which doesn't redundantly serialize the field with it's custom name in my case. If for some reason you wanted to ensure that the field was serialized using it's custom field name though.. there doesn't appear to be a way to do that. I'm

Re: Bug in model inheritance?

As to whether it's a bug or not I have no idea, though it seems so. If you use: entity = models.OneToOneField(Entity, parent_link=True, primary_key=True) it will create the primary key in both Kid and Adult tables, which sounds like what you want? On Tue, Sep 28, 2010 at 1:06 PM, phill

Bug in model inheritance?

This looks quite a bit like a bug, but we may be off the reservation in terms of how we're using the product. (Disclaimer: I'm relatively new to Django, and extremely new to the codebase that I ran into this on). We've got a form of schema-inheritance going on in this project in order to

Re: Multi-table + Abstract Model Inheritance

Well, on the surface this works. I'm sure if anything unexpected happens I'll be back. On Sep 17, 8:34 am, ringemup wrote: > Sure, it's easy enough to find out if it works in a general sense -- > but I'm also concerned about running into subtle bugs down the road, > and

Re: Multi-table + Abstract Model Inheritance

Sure, it's easy enough to find out if it works in a general sense -- but I'm also concerned about running into subtle bugs down the road, and having to restructure my entire database as a result. On Sep 17, 4:15 am, bruno desthuilliers wrote: > On 16 sep, 22:11,

Re: Multi-table + Abstract Model Inheritance

On 16 sep, 22:11, ringemup wrote: > Is it possible for a model to inherit from an abstract model, which in > turn inherits from a non-abstract model? I don't thinks so, but I may be wrong. Now nothing prevents you from trying by yourself, it shouldn't take long to find out

Multi-table + Abstract Model Inheritance

Is it possible for a model to inherit from an abstract model, which in turn inherits from a non-abstract model? Here's an example. In this case, the reason for using multi-table inheritance rather than an explicit one-to-one relation would be that the office addresses would be editable via

Re: model inheritance, abtract=True

On Aug 5, 2010, at 3:15 PM, Roald de Vries wrote: On Aug 5, 2010, at 3:00 PM, Emily Rodgers wrote: On Aug 5, 1:50 pm, Roald de Vries wrote: Dear all, I have the following error, and don't know what it means: Error: One or more models did not validate:

Re: model inheritance, abtract=True

On Aug 5, 2010, at 3:00 PM, Emily Rodgers wrote: On Aug 5, 1:50 pm, Roald de Vries wrote: Dear all, I have the following error, and don't know what it means: Error: One or more models did not validate: update.personupdate: 'address' has a relation with model

Re: model inheritance, abtract=True

On Aug 5, 1:50 pm, Roald de Vries wrote: > Dear all, > > I have the following error, and don't know what it means: > >      Error: One or more models did not validate: >      update.personupdate: 'address' has a relation with model Address,   > which has either not been

model inheritance, abtract=True

Dear all, I have the following error, and don't know what it means: Error: One or more models did not validate: update.personupdate: 'address' has a relation with model Address, which has either not been installed or is abstract. I did a pretty big refactoring, but I think the

Re: Model inheritance and simple access

e > a method in the parent as a property which returns the correct child > type.  Works for now, would be nice if the framework kept track of it, > but it's a rare case. > > J > > On Jun 8, 12:41 pm, Dan Harris <dih0...@gmail.com> wrote: >> Not sure if this will work as I do

Re: Model inheritance and simple access

case. J On Jun 8, 12:41 pm, Dan Harris <dih0...@gmail.com> wrote: > Not sure if this will work as I don't usually do much with model > inheritance but according to docs > at:http://docs.djangoproject.com/en/dev/topics/db/models/#id7 > this might work (not pretty, but somewhat mini

Re: Model inheritance and simple access

Not sure if this will work as I don't usually do much with model inheritance but according to docs at: http://docs.djangoproject.com/en/dev/topics/db/models/#id7 this might work (not pretty, but somewhat minimal code)... p = Parent1.objects.get(id=1) try: p.childa.basemthod() except: try

Re: Model inheritance and simple access

gt; > > On Tue, Jun 8, 2010 at 8:05 PM, John M <retireonc...@gmail.com> wrote: > > I've gotten model inheritance working just fine, but was hoping > > someone could confirm the best way to access the model. > > > When I have a Base model which has a ForeignKey to a pare

Model inheritance and simple access

I've gotten model inheritance working just fine, but was hoping someone could confirm the best way to access the model. When I have a Base model which has a ForeignKey to a parent table, and that base model has inherited models after it, how can I refer to only one name when referencing

Re: Model inheritance foreign key user

You are right but it would not change his problem. If 2 or more classes inherit from a class with a foreignkey or a manytomany, there will be a conflict in the related name Le 4 avr. 2010 à 14:11, Daniel Roseman a écrit : On Apr 3, 10:37 pm, Fredrik

Re: Model inheritance foreign key user

On Apr 3, 10:37 pm, Fredrik wrote: > What I want is to "automatic" add an owner to every object.. > > Is there another way to accomplish the same? > > Fredrik > Do you need the PersistentModel field to exist in a separate table? It sounds to me as if that would be better

Re: Model inheritance foreign key user

Le 3 avr. 2010 à 23:37, Fredrik a écrit : What I want is to "automatic" add an owner to every object.. Is there another way to accomplish the same? I see. I have had a similar problem. I have tried a similar solution with exactly the same effect. I could have

Re: Model inheritance foreign key user

What I want is to "automatic" add an owner to every object.. Is there another way to accomplish the same? Fredrik On Apr 3, 10:48 pm, Thierry Chich wrote: > I think that if you want make inheritance it is because you want to   > have others subclasses. But then, your

Re: Model inheritance foreign key user

I think that if you want make inheritance it is because you want to have others subclasses. But then, your related name will be same for all the subclasses. There is no solution with the stable version. In the dev version, it is possible to add the origin class name in the related_name. It

Model inheritance foreign key user

Hi, I want to use it like this: """ class PersistentModel(models.Model): deleted = models.BooleanField(default = False) date_created = models.DateTimeField(default=datetime.now) date_edited = models.DateTimeField(default=datetime.now) owner = models.ForeignKey(User) class

Strange behaviour with select_related and model inheritance

Hello, Here is an extremely simple scenario: class Base(models.Model): f1 = models.CharField(max_length=64) class A(Base): f2 = models.CharField(max_length=64) class B(models.Model): f3 = models.CharField(max_length=64) b = models.OneToOneField('A', null=False,

Re: Model Inheritance - best practice for templates?

mis-clicked, continuing: @register.filter def A_get_B(instance):     if isinstance(instance, B):         return instance.b     try:         return instance.b     except B.DoesNotExist:         return None and lastly, the template: {% with a|A_get_B as b %} {% if b %} .. work with b {%

Model Inheritance - best practice for templates?

All, Currently I'm working with the following 2 models: class A (models.Model): ... class B (A): somefield = ... I have a generic views with querysets defined as: url(r"A/view/(?P\d+)/$", "django.views.generic.list_detail.object_detail", dict(queryset = A.objects.all(), template_name =

Re: Model inheritance

On 12 Sty, 20:52, a b wrote: > Hi, > > I have three models: > Product > SimpleProduct that extends Product > GroupProduct that extends Product and have ManyToMany relation with > SimpleProduct > > The reason to use the base Product model is so I can use paging. > Is it

Model inheritance

Hi, I have three models: Product SimpleProduct that extends Product GroupProduct that extends Product and have ManyToMany relation with SimpleProduct The reason to use the base Product model is so I can use paging. Is it possible to make a query that gives a list of GroupProducts and

Re: Model inheritance - filtering base model only

a simple solution would be to put pass the contentype id and object id around in your url scheme domain.com/ct_id-object_id/ from there you can get the content type, which will be able to tell you the model, type, and give you the object. type = ContentType.objects.get(pk=ct_id) model =

Re: Model inheritance - filtering base model only

On Mon, Nov 23, 2009 at 9:09 AM, lfrodrigues wrote: > I guess this solution works but for +50 the performance should be > terrible... > > Shouldn't django have some option for this? Could you set a field's value which is true for one, and false for the other?

  1   2   3   >