Hey Waldemar and everyone else, termie here, I'm an App Engine developer and
worked on the Django Helper library.
This is something I'm deeply interested in (and many other app engine folk
agree) and I'd like to work together.
My initial goals are to get some concrete experiments up so that the people
on this thread have something to point at for their arguments.
I'm more of a git person and am used to the github workflow, but I'm not
against checking out and trying to collaborate on your bitbucket project.
--andy
On Sat, Aug 15, 2009 at 2:42 AM, Waldemar Kornewald wrote:
>
> Hi Malcolm,
> first of all, we'll soon start with a few experiments and since you
> wanted to play around with some code, too, could you please tell us
> your bitbucket username, so we can give you write access to the
> repository?
>
> On Aug 11, 4:07 am, Malcolm Tredinnick
> wrote:
> > Things like a ListField aren't required. They could easily enough be
> > done as a standard custom field, but support for every field that's
> > possible in a particular database backend isn't our goal at the moment
> > and we don't add stuff to Django for that reason. Django runs on
> > app-engine would mean that existing applications run with the existing
> > field types. Not that every possible app-engine storage structure is
> > emulated in Django.
>
> ListField is a critical data type in non-relational DBs. There needs
> to be a standard that works across all non-relational backends and
> that makes it possible to switch back to an SQL-backed Django. How do
> you want to solve that without integrating ListField into Django?
>
> > Batch delete() is already pretty much what happens. Batch updates
> > already exist and batch saving is an often enough requested feature that
> > it's likely to happen in the near future (I can imagine what an API for
> > that might look like, for example).
>
> Unless I've misunderstood something, there's a problem with the
> current batch-delete/update operations: You can't pass existing model
> instances, but only PKs. In the worst case, all rows have to be re-
> fetched from the DB and the models must be re-instantiated - just to
> send signals. This could be a costly operation on non-SQL DBs, so if
> one already has a list of instances he wants to delete they should be
> reused.
>
> Bye,
> Waldemar Kornewald
> >
>
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
