My recommendation is to use the datastore mock that ships with the SDK as well as the version of Jetty that ships with the SDK. This is going to be the closest thing you'll get to what's in production. You're likely looking at MySQL because the local datastore does not meet some development need of yours - I'd recommend opening an issue rather than replacing it in dev mode.
On Thu, Jan 14, 2010 at 12:55 PM, Ian Marshall <[email protected]>wrote: > Thanks for that warning, Ikai. Noted. I am aware of many of the > difference between MySQL and the GAE datastore (mock or production). > And when I see your reasons all at once, it does make me cringe at my > choice of MySQL as my local dev back-end datastore. Regular runs under > my local GAE dev server should catch most issues early (here's > hoping). > > Can you think of suitable local datastores that I could use when > running my Java web app from my NetBeans IDE under Tomcat whilst > coding? > > Regards, > > Ian > > -- > 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]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- Ikai Lan Developer Programs Engineer, Google App Engine--
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.
