I switched to sqlite3, here is the behavior: Non administrator: - Creates the rdbms file on custom location, populates the file - Throws an "unable to read datastore file" exception
Administrator: - Works perfectly It wasn't working for non-sqlite3 even with the administrator privileges and it works with sqlite3 only with administrator priv. Very strange but I'm glad it works On Saturday, April 7, 2012 11:14:44 PM UTC+3, Kaan Soral wrote: > > I guess my development efforts were concentrated on non-db stuff all these > time so I am just realizing this now. > > Whenever I reset a project, all of the new data is lost, I see that > dev_appserver.datastore is not written. > > This may be happening since I upgraded to 1.6.4 or it is probably > unrelated since I didn't see anyone with this problem. > > Any ideas? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/6xgU5LN2_4IJ. To post to this group, send email to google-appengine@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.
