Hi Tim, your question can be easily answered by going to the bugs database (http://code.google.com/p/googleappengine/issues) and query for sqlite. At least bugs: 3232, 3265, 3124 and 3689 are showstoppers for me. You probably do not use these features in your applications and you are doing fine. Yet, these are documented features working with the default dev datastore and production datastore and therefore I feel that my comment and Ubaldo's response are justified.
I do not want to see Google make sqlite the default datastore without addressing these issues. PK http://www.gae123.com On Oct 28, 5:32 am, Tim Hoffman <zutes...@gmail.com> wrote: > Hi > > I am regularly backing up two projects from live site to dev. (55,000 > and 90,000 entities each ) > and uploading to sqlite dev server. I am not currently experiencing > any major problems. > > The problems I see tend be around transaction write through (ie puts > appear to happen immediately not at the end of the transaction) and > over remote_api. > but are not show stoppers. > > What sort of problems are stopping you ? > > Rgds > > Tim > > On Oct 28, 5:23 pm, Ubaldo Huerta <uba...@gmail.com> wrote: > > > > > 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 <p...@gae123.com> 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 google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
