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 -~----------~----~----~----~------~----~------~--~---
