Re: app engine db backend project
I've been looking into this too last night. Though I never before looked into a backend and I'm not on qsrf branch, after looking into the trunk's backends, I can tell that they're a tad over my head. It's a shame that this is not documented (though I'm not whining at the devs for not writing it, I recon there are more important things to do than document maybe-unstable low-level components). If I can do anyhing to help, I'm in. ~ Chris El mar, 08-04-2008 a las 15:00 -0700, Greg Taylor escribió: > This would be great, I'd love to see this although I'm not really > experienced enough to help much. > > On Apr 8, 10:21 am, "Peter Baumgartner" <[EMAIL PROTECTED]> wrote: > > Anybody interested in starting an app engine/big table db backend > > project? Should be interesting and might help pave the way for some > > other non-traditional databases like CouchDB or SimpleDB. While I'm > > not a database expert, I'm sure I can chip in. > > > > It seems like most of the basic functionality is already there and > > more advanced queries could be simulated with multiple queries and > > some magic on the backend. > > > > -- > > Pete > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
On Wed, Apr 9, 2008 at 1:24 PM, binaryj <[EMAIL PROTECTED]> wrote: > > i plan to help on doing this but right now i dont have the time and a > working app account to do this. I can get you developer access on an account when you have time, just let me know off list. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
its better to use the existing code structure as much as possible. if i were u i would first make the cursor return a gql comparable object. i plan to help on doing this but right now i dont have the time and a working app account to do this. when i am done making all my websites ill give porting the models to bigtable On Apr 9, 4:25 am, "Peter Baumgartner" <[EMAIL PROTECTED]> wrote: > Thanks Eric, > > One thing I'm struggling with is figuring out where to start coding :P > > All the other backends start by initializing a connection and then > handling things through a cursor as far as I can tell. GQL doesn't > really need any of this, so can I skip it altogether or should I > emulate a cursor in Python? > > -- > Pete > > On Tue, Apr 8, 2008 at 4:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Doh! I see that you're using the queryset-refactor branch already. > > That teaches me to post before reading. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
Thanks Eric, One thing I'm struggling with is figuring out where to start coding :P All the other backends start by initializing a connection and then handling things through a cursor as far as I can tell. GQL doesn't really need any of this, so can I skip it altogether or should I emulate a cursor in Python? -- Pete On Tue, Apr 8, 2008 at 4:45 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Doh! I see that you're using the queryset-refactor branch already. > That teaches me to post before reading. > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
Doh! I see that you're using the queryset-refactor branch already. That teaches me to post before reading. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
FWIW, I would probably start out with the queryset-refactor branch, as it has made some great strides in increasing database modularity. Looking at the dummy and sqlite backends in that branch should be a pretty good starting point. Remember than on Django trunk (or queryset-refactor), the DATABASE_ENGINE can be an arbitrary python path to your database engine, so placing it anywhere on your PYTHONPATH should be fine. I'm not sure if you'll be able to fully implement a backend, however, because there are some serious restrictions on the queries against BigTable. Case in point: it may be difficult discover a way to implement the exclude() filter on the new backend, as there is no "!=" operator in GQL. However, any backend would be better than none :) -Eric Florenzano --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
This would be great, I'd love to see this although I'm not really experienced enough to help much. On Apr 8, 10:21 am, "Peter Baumgartner" <[EMAIL PROTECTED]> wrote: > Anybody interested in starting an app engine/big table db backend > project? Should be interesting and might help pave the way for some > other non-traditional databases like CouchDB or SimpleDB. While I'm > not a database expert, I'm sure I can chip in. > > It seems like most of the basic functionality is already there and > more advanced queries could be simulated with multiple queries and > some magic on the backend. > > -- > Pete --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
Never having looked under the hood of the database backends, my head is swimming a little bit trying to find a place to get started. I'm working on the queryset-refactor branch and using the sqlite3 backend as a template. Any devs that can point me in the right direction? -- Pete On Tue, Apr 8, 2008 at 8:26 AM, Marty Alchin <[EMAIL PROTECTED]> wrote: > > > On Tue, Apr 8, 2008 at 10:21 AM, Peter Baumgartner <[EMAIL PROTECTED]> wrote: > > Anybody interested in starting an app engine/big table db backend > > project? Should be interesting and might help pave the way for some > > other non-traditional databases like CouchDB or SimpleDB. While I'm > > not a database expert, I'm sure I can chip in. > > > > It seems like most of the basic functionality is already there and > > more advanced queries could be simulated with multiple queries and > > some magic on the backend. > > I'd love to see it happen, even if as an academic exercise, but I > don't have the time right now to work on it. I do know a lot about > making magic with models though, so I'll keep an eye on whatever > happens and chime in where I think I can help. > > -Gul > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: app engine db backend project
On Tue, Apr 8, 2008 at 10:21 AM, Peter Baumgartner <[EMAIL PROTECTED]> wrote: > Anybody interested in starting an app engine/big table db backend > project? Should be interesting and might help pave the way for some > other non-traditional databases like CouchDB or SimpleDB. While I'm > not a database expert, I'm sure I can chip in. > > It seems like most of the basic functionality is already there and > more advanced queries could be simulated with multiple queries and > some magic on the backend. I'd love to see it happen, even if as an academic exercise, but I don't have the time right now to work on it. I do know a lot about making magic with models though, so I'll keep an eye on whatever happens and chime in where I think I can help. -Gul --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
