I'm late on the topic, sorry. :-)
Just tried BDBDatastore yesterday. A good reason to use it is to have
a local/development datastore with better performance. The default one
provided with the SDK performs very poorly with large datasets.
BDBDatastore can do it much better, and so is very welcome
On Apr 18, 11:34 pm, Dag wrote:
> Very cool, but I don't know if this will solve the 'practical lock in'
> problem for GAE python. It may be hard to find a hosting provider that
> offers django along with long-running java processes.
I don't expect this to be used by people wanting to host on sh
Very cool, but I don't know if this will solve the 'practical lock in'
problem for GAE python. It may be hard to find a hosting provider that
offers django along with long-running java processes.
Still, GAE-J developers now have a reasonable alternative and maybe
some of your efforts can be appli
On Apr 17, 5:50 pm, johnP wrote:
> Quick question (I have not looked at your datastore at all yet) -
>
> Can using your datastore eliminate the limit of 1000 entities on a
> fetch? Thanks -
BDBDatastore itself doesn't enforce any limits on results returned,
but it suffers all the same problems
Quick question (I have not looked at your datastore at all yet) -
Can using your datastore eliminate the limit of 1000 entities on a
fetch? Thanks -
johnP
On Apr 17, 8:06 am, Nick Johnson wrote:
> Recently I've been working on a replacement datastore backend for App
> Engine, to allow hostin
