Partly true, partly not. Usage of ORM in PHP not common as in Java, but most of the PHP based system has a an abstraction layer upon the database, and if you change it, you can use your existing system on GAE. For example you can run Wordpress on AppEngine with Quercus with a relatively small pain (see http://wordpress-on-quercus.appspot.com/wordpress-2.7.1/ ).
If you develop a new application, you can use ORM which hides the real database implementation. For example LWorm ( http://code.google.com/p/lworm/) is really small and easy to use abstraction tool. If you use it, you can use your application in a standard LAMP environment with MySQL, or on AppEngine with Quercus without any pain. Thirdly, it is possible to use memory mapped SQL databases (like HSQLDB) as a storage. In this case the db is stored in datastore as a blob. Not so efficient, but it can work with small databases. Bu, as I know, Google plans to support SQL on AppEngine (maybe only in the AppEngine for Business). So, I think PHP on AppEngine is not an impossible or meaningless thing, and not wronger than Python on AppEngine. Quercus is existing thing, you can run PHP on AppEngine with it. It is GPL-ed. So, I think, the only think what Google should do is officially support it on AppEngine. Maybe it would be enough to change the sdk, and create a build script which makes a war which includes Quercus and the PHP code. It doesn't songs too difficult, so I don't understand why not supported PHP on AppEngine. (PHP support is one of the most needed feature on the issues list.) -- 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/-/nvnn6N7lcfMJ. 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.
