Hey everyone, I can't see this ending well. App Engine's datastore is NOT an RDBMS. It is schemaless. There are already enough differences between using the local datastore mock and the production datastore. Introducing MySQL as the local development backend is just going to introduce a lot of unnecessary risk in your project and a lot of wackiness as soon as you go into production. I'm not even sure how your indexes can be generated, or how you can catch all the hard errors that will be thrown when you work with transactions for entities not in an entity group, or indexed List properties.
I'm sure you have a good reason for wanting to do this, but the bad really outweigh the good here. On Thu, Jan 14, 2010 at 1:54 AM, Ian Marshall <[email protected]>wrote: > Hi ivanceras, > > > At least I'm having a progress here > ----------------------------------- > Good! > > > Here is the Postgresql error log > -------------------------------- > Sorry, I know nothing about Postgresql. I shall leave comments about > this part of your post to others. > > > Here is the error logs > ---------------------- > I think that the clue is in your own statement "Due to maybe it is not > allowed in app engine white list." Examining your stake trace, we have > the DataNucleus RDBMS making a connection with/using the MySQL Java > connector. This is fine, but Google AppEngine (GAE) code is also > involved here. It shouldn't be. > > As you know, GAE will not allow use of MySQL directly as the > datastore. Somehow you are involving GAE, when I guess that instead > you want to run your web app in Eclipse whilst connecting to your > MySQL database. In that case, you cannot run this app in GAE. > > When I use NetBeans, I launch my web app from within NetBeans with my > MySQL connection configured as per my "jdoconfig.xml" file using a > development Persistence Manager Factory (PMF) name. When I am ready to > run the web app from within my local GAE development server, I change > the PMF name used in my code by configuration and rebuild my app. My > builder constructs my \war folder every time, so now after building I > simply launch my GAE server (using a command in a Windows command > prompt window) whilst pointing to the correct folder. There is now no > MySQL involvement with the web app, and my datastore is now a local > BigTable database. > > Am I on the right lines, and does this help you? > > > Conclusion > ---------- > If anyone out there uses Eclipse and a MySQL database for developer > testing before unleashing on a local GAE development server, I am sure > that ivanceras would welcome your contribution. > > > Cheers, > > 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.
