I second this opinion. Not sure how many people have switched to sqlite but my guess is that only "early adopter" types have done so. I constantly struggle to trim down the amount of data I use in local datastore because beyond a few 1000's entities, it gets really slow, specially startup time. I'm resisting to take the plunge when I saw the issue about __key__ queries which hasn't even been acknowledged.
The sensible way to develop locally is to bulk download production data to use it for local development. That's not an option of mid size sites. I was hoping for more active development in it, and that by now use_sqlite would have been the default option. Mystified by how little outcry I see about this. I'd like to get a feel for usage of use_sqlite option, any other bugs?. Have you switched? Would you recommend it? Thanks On Sep 9, 5:10 am, PK <[email protected]> wrote: > It has been since April with SDK 1.3.3 that this this exciting feature > was released but I still cannot switch to it. I do not want to > enumerate the issues here, search for 'sqlite' in the issues database > and you will see that important aspects of the datastore (like queries > on __key__ etc) do not work correctly. > > With bigger test datasets the development datastore is really slow and > I have been having high hopes for the sqlite based implementation. Is > there any plan to fix these showstopper issues and make this feature > really usable? > > Thanks > PKhttp://www.gae123.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
