On Jan 15, 5:38 pm, Sebastian Bauer <ad...@ugame.net.pl> wrote:
> I think ORM supposed to have save insert and update:
>
> save(force_insert=False,force_update=False)
> update() == save(force_update=True)
> insert() == save(force_insert=True)
>
> in that situation we could have clean code and we know that update is
> realy update on DB
>
> i now we can have save(force_update=True) but update() looks better and
> we have insert() already
>
> IMHO save() is only wrapper for save_base()
>
Those look like great methods to have, but since Django has already
hit 1.0 with a statement about API stability, I don't want the core
developers changing it on me. I don't think the ORM is wrong, just
designed differently than other ORMs.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
