Cool, that's exactly what I mean. I just wrote this comment because at the moment, I do not have the possibility to test it myself. I have seen this part of the Campfire video but didn't realize, that those configuration changes are exactly the one's I was looking for (actually, I thought this couple was the worst part of the presentation! Shame on me

Anyways, I was investigating this topic a bit further and think, that it would be much better to do it with the “Secure Data Connector”. In one part of the Campfire, a guy from Oracle connects to its database and loads data. The advantage is, that the data is sent encrypted trough the internet. The moderator mentions shortly, that they will provide over 50 connectors. Let's see what databases they gonna support. Cheers

Cool, that's exactly what I mean. I just wrote this comment because at the moment, I do not have the possibility to test it myself. I have seen this part of the Campfire video but didn't realize, that those configuration changes are exactly the one's I was looking for (actually, I thought this couple was the worst part of the presentation! Shame on me

Anyways, I was investigating this topic a bit further and think, that it would be much better to do it with the “Secure Data Connector”. In one part of the Campfire, a guy from Oracle connects to its database and loads data. The advantage is, that the data is sent encrypted trough the internet. The moderator mentions shortly, that they will provide over 50 connectors. Let's see what databases they gonna support. Cheers

Google has incentive to keep all of your data on their servers by claiming power in the cloud and bind/support your development through GAE.

Given all of this, there's nothing stopping you from writing your own export/backup mechanism. You could created a crond job that iterates over all of the objects in your datastore and generate a big SQL file that you could use to import to MySQL. It would development require some work but might be worthwhile if you are concerned that you may want to move off of GAE in the future.
That said, give it and shot! I'd be interested in if it's possible.

Thanks for the short and informative feedback about the new possibilities with “Google App Engine”. Since they use the “DataNucleus Access Platform” to store JDO-annotated objects I'm wondering, if it would be possible to store the objects in an RDBMS. Of course “DataNucleus Access Platform” itself supports several of those databases (e.g. MySQL, PostgreSQL,…) but I'm curious, if “Google App Engine” includes those extensions.

Would it possible to adapt the “jdoconfig.xml” configuration file in order to use my own database so that I still “own” my data? It would be so much easier to backup the data and one would have full control over the data. I guess, the config-file should include something like this:

<persistence-manager-factory name=”transactions-optional”>
<property name=”javax.jdo.PersistenceManagerFactoryClass”
value=”org.datanucleus.jdo.JDOPersistenceManagerFactory”/>
<property name=”javax.jdo.option.ConnectionDriverName”
value=”com.mysql.jdbc.Driver”/>
<property name=”javax.jdo.option.ConnectionURL”
value=”jdbc:mysql://localhost/datanucleus?useServerPrepStmts=false”/>
<property name=”javax.jdo.option.ConnectionUserName”
value=”username”/>
<property name=”javax.jdo.option.ConnectionPassword”
value=”password”/>
<property name=”javax.jdo.option.Optimistic”
value=”false”/>
<property name=”datanucleus.autoCreateSchema”
value=”true”/>
</persistence-manager-factory>

I got this example from here: http://www.datanucleus.org/products/accessplatf...

Thanks and looking forward to hear from you,
Alain