Putting django on Amazon DB
John M
starting a BETA of Amazon SimpleDB(tm)- Limited Beta, which turns their
S3 into a simple database.
I know the developers for django are pretty busy, but how hard would
it be to put this simple DB into django?
http://www.amazon.com/gp/browse.html?node=342335011
James Bennett
> I know the developers for django are pretty busy, but how hard would
> it be to put this simple DB into django?
Django has the ability to use a database backend not defined as part
of Django itself, so the best plan for this would be for you and
others who are interested in the feature to write up an implementation
and offer it for use. If/when it matures and has a proven track record
of being stable and useful (and has someone willing to commit to
maintaining it long-term), then it'll be time to talk about whether it
belongs as part of Django proper.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Justin Bronn
> starting a BETA of Amazon SimpleDB(tm)- Limited Beta, which turns their
> S3 into a simple database.
>
> I know the developers for django are pretty busy, but how hard would
> it be to put this simple DB into django?
> in the feature to write up an implementation and offer it for use
your efforts using the queryset-refactor branch.
-Justin
Mitch....@gmail.com
I've written a module supporting SDB for my boto library and I'd love
to see a tighter connection between Django and SimpleDB.
I'm certainly not a Django expert but I did try to slot SimpleDB into
Django in a way that would allow me to define models in Django and
have it just work. Admittedly, I spent a total of probably two hours
on this but there were definitely some impedance mismatches between
the two. I'd love to work with someone who has a deeper understanding
of Django to see if we can map even a subset of Django's ORM to
SimpleDB.
Mitch
Empty
of when I received the announcement today. You do great work with the
boto library and I'm excited to see that you're looking into this.
As an aside, if the database backends were truly pluggable, like
sessions, then we could prove the stability, usability, and commitment
of the implementation without core commitment ahead of time. A brief
search showed that this was discussed here:
...and while I'm at it I would really like to pluggable cache backends too. :)
Michael
blog.michaeltrier.com
On Dec 14, 2007 6:41 PM, Mitch....@gmail.com
James Bennett
> As an aside, if the database backends were truly pluggable, like
> sessions, then we could prove the stability, usability, and commitment
> of the implementation without core commitment ahead of time. A brief
> search showed that this was discussed here:
As I've already said, you can write a database backend, right now, and
use it with Django, right now, without needing it to be part of Django
itself. The DATABASE_BACKEND setting will -- in addition to the named
backends which ship with Django -- accept a dotted Python path to a
backend module and use that. All you need to do is write the code.
Empty
>
> On Dec 14, 2007 5:55 PM, Empty <mtr...@gmail.com> wrote:
> > As an aside, if the database backends were truly pluggable, like
> > sessions, then we could prove the stability, usability, and commitment
> > of the implementation without core commitment ahead of time. A brief
> > search showed that this was discussed here:
>
> As I've already said, you can write a database backend, right now, and
> use it with Django, right now, without needing it to be part of Django
> itself. The DATABASE_BACKEND setting will -- in addition to the named
> backends which ship with Django -- accept a dotted Python path to a
> backend module and use that. All you need to do is write the code.
I didn't read that from your original post and the investigating I did
I did not find that, so that's great to know. Thanks so much.
Michael Trier
blog.michaeltrier.com