On Wednesday, June 11, 2014 2:16:06 AM UTC+2, Craig de Stigter wrote:
>
> I reserve judgment on whether STI should be included in core. It works
> fine in a third-party app. Some better support for it in core would be
> helpful, since currently I'm relying on some unsupported stuff that the
>
Late reply I know but I see a lot of FUD in this thread and I want to try
and clear it up.
> in the general case, STI means you have to make almost all the fields in
your model NULLable. You lose any semblance of having an actual database
schema, and end up writing a whole lot of code to re-im
On 6 juin 2014, at 09:42, Thomas Güttler wrote:
> I think it is a "not invented here" syndrome: Ruby on Rails did it before.
> That's
> a reason to do it different.
The reason is more simple.
Rails was designed around MySQL, a database with a rather casual relationship
to data integrity. It wi
Let me expand on Russell's expletives:
On Friday 06 June 2014 09:42:15 Thomas Güttler wrote:
>
> I guess a lot of developers don't want to hear the next lines:
>
> I think it is a "not invented here" syndrome: Ruby on Rails did it before.
> That's a reason to do it different.
>
This does deser
On Fri, Jun 6, 2014 at 3:42 PM, Thomas Güttler wrote:
>
>
> Am 26.05.2014 00:50, schrieb Craig de Stigter:
>
> If you ignore STI, I think it is quite straightforward to solve this with
>>> a
>>>
>> parent model class which adds a type field, and manager methods to add the
>> select_related calls
Am 26.05.2014 00:50, schrieb Craig de Stigter:
If you ignore STI, I think it is quite straightforward to solve this with a
parent model class which adds a type field, and manager methods to add the
select_related calls and "interpret" the type field properly; so I don't see an
immediate need f
> If you ignore STI, I think it is quite straightforward to solve this with
a
parent model class which adds a type field, and manager methods to add the
select_related calls and "interpret" the type field properly; so I don't
see an
immediate need for inclusion in core.
Well, you don't need
On 05/22/2014 11:13 AM, Shai Berger wrote:
Any thoughts on this idea?
Instinctively -- isn't it possible to achieve the same things today by
overriding __new__ ?
My understanding is that achieving all the same things isn't possible.
The problem is that inside __new__ it is impossible to know i
On Thursday 22 May 2014 11:05:24 Anssi Kääriäinen wrote:
> I think it is time to add a new model classmethod from_db() to Django.
>
> The idea is to allow customization of object initialization when loading
> from database. Instead of calling directly model.__init__ from the queryset
> iterators,
I think it is time to add a new model classmethod from_db() to Django.
The idea is to allow customization of object initialization when loading
from database. Instead of calling directly model.__init__ from the queryset
iterators, Django calls model_cls.from_db(). The default implementation
cal
On 05/16/2014 04:46 AM, Shai Berger wrote:
> On Monday 12 May 2014 12:27:01 Thomas Güttler wrote:
>> Single Table Inheritance is used by ruby-on-rails and SQLAlchemy.
>>
>> Are there reasons why it is used in django?
>>
>
> Essentially, STI is a form of database denormalization. I think Django sho
On Monday 12 May 2014 12:27:01 Thomas Güttler wrote:
> Single Table Inheritance is used by ruby-on-rails and SQLAlchemy.
>
> Are there reasons why it is used in django?
>
Essentially, STI is a form of database denormalization. I think Django should
not encourage this.
> I would love to see a p
This is already merged.
https://docs.djangoproject.com/en/1.6/topics/db/models/#multi-table-inheritance
Am Montag, 12. Mai 2014 11:27:01 UTC+2 schrieb guettli:
>
> Single Table Inheritance is used by ruby-on-rails and SQLAlchemy.
>
> Are there reasons why it is used in django?
>
> I would lov
On Thu, May 15, 2014 at 4:11 PM, Christian Schmitt
wrote:
> This is already merged.
>
> https://docs.djangoproject.com/en/1.6/topics/db/models/#multi-table-inheritance
>
MTI is not STI, nor is it polymorphic.
Cheers
Tom
--
You received this message because you are subscribed to the Google Gro
Single Table Inheritance is used by ruby-on-rails and SQLAlchemy.
Are there reasons why it is used in django?
I would love to see a polymorphic inheritance solution in django.
I know that there are third party apps which provide this, but
something like this should be in the core.
There was so
15 matches
Mail list logo
