Django - how to duplicate all fields definitions from one model to another without inheritance

Question

I need to define a extact copy of existing model with it's own table and all columns without Django inheritance mechanism. Otherwise it uses OneToOne relation and keeps all duplicated fields in parent table, that I definetly don't need. I just want to avoid repeating model fields and method definitions for my second model.

Any suggestions?

jpic · Accepted Answer · 2012-09-14 20:42:26Z

6

One way would be to create abstract base model with common attributes. Then create one model corresponding to parent model in current app.

Create another model for the duplicate model with same base class (and some other fields).

Not elegant though!

edited Sep 14, 2012 at 20:42

jpic

33.5k5 gold badges114 silver badges114 bronze badges

answered Sep 14, 2012 at 20:34

Rohan

53.5k12 gold badges95 silver badges89 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Andre Bossard · Accepted Answer · 2012-09-16 11:57:47Z

0

Did you look at Mixins?

With them you can mixin the fields of a class to your Model class and still inherit form a regular Base class. And you can mixin fileds from different classes and thus maybe make a good structure.

http://eflorenzano.com/blog/2008/05/17/exploring-mixins-django-model-inheritance/

answered Sep 16, 2012 at 11:57

Andre Bossard

6,3011 gold badge38 silver badges53 bronze badges

5 Comments

ramusus Over a year ago

The problem is the same - inheritance from mixins classes or probably any non-abstract classes makes OneToOne relation and keeps all inherited fields in parent table, that I definetly don't need.

Andre Bossard Over a year ago

Make a Mixin containing all the fields and make it abstract. Make a Base Class. Make the two concrete classes and inherit form the field-less base class and add the mixins each.

ramusus Over a year ago

what difference from the first answer with inheritance from abstract class? could you show example of structure in your answer?

Andre Bossard Over a year ago

Technically, there is no difference. But it allows you to have different base classes for example. Why don't you accept the first answer?

ramusus Over a year ago

I'm still thinking about the way I prefer

Collectives™ on Stack Overflow

Django - how to duplicate all fields definitions from one model to another without inheritance

2 Answers 2

Comments

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related