Skip to main content

ORM on Google App Engine with Open BlueDragon

The work to get OpenBD running on Google App Engine has been going great, and just today we added details to the OpenBD wiki covering how to use the GAE Datastore with OpenBD. Kudos to Vince Bonfanti for all the hard work on this! We should have a downloadable GAE-compatible version of OpenBD available soon.


Hi Matt,

Since the GAE datastore isn't a relational database, the OpenBD API isn't technically an ORM (Object-Relational Mapping). It's more accurate to describe the GAE datastore as an object database, into which the OpenBD API allows you to store CFC instances.

Hello Matt !

Reading on a Sunday about 'CFML without the ORM hassle' has made me literally cry some

tears of joy :-) ... Because my appetite for the seemingly shining 'Land of OODBMSes' has

been whetted for some while now !

But further reading and thinking about this 'OpenBD CFML GAE Datastore' thingie has

quickly have me sobered ...

What I like about this new avenue:

- The 'kind' approach

- The seemingly sheer simplicity of the GAE Datastore API

What I dislike:

- No 'unequal' operator in the 'where clause'

- Much too little information:

- What about GAE Datastore 'ACID' compliancy ?

- What about cascading deletes and referential integrity ?

Asked another way round: Is it already prime time for this 'OpenBD CFML GAE Datastore'

thingie ? That is can I achieve with this thingie everything as easy - or easier for that

matter - as if using the traditional 'RDBMS with ORM' approach ?

Cheers and Tschüss


Hello Kai,

Let me try to answer some of your questions for you. Google claims that the datastore is "strongly consistent" but don't really elaborate on this point:

The GAE datastore supports transactions, but this isn't supported by the OpenBD API yet (it will be in the future):

The GAE datastore supports relionships between objects, but this isn't support by the OpenBD API yet (it will be in the future):

With the current OpenBD API, if a CFC contains a reference to another CFC, the referenced CFC is stored as an embedded object within the "parent" CFC. The two CFCs are not stored independently (if you write the "embedded" CFC to the datastore separately from the "parent", the "embedded" CFC will effectively be stored in the datastore twice).

Both the GAE datastore and OpenBD API are at the early stages of development and are sure to evolve and mature as time progresses. The best thing for you to do is use it and let us know what you like and dislike, and how you'd like to see it improved.

Hello Vince !

Thanks for the clarifications; unfortunately I cannot afford myself to play around with evolving solutions; what I need are rock-solid, robust approaches; so I will keep this 'OpenBD CFML GAE Datastore' thingie on my radar, but won't use it as of now.

Thanks and Tschüss


@Vince--thanks for pointing that out. I did debate calling it "ORM" since the "R" is a bit of a misnomer, but it seemed the quickest way to get the point across that you can save CFCs to the GAE Datastore without having to worry about the mechanics of it. Sorry if that caused confusion for anyone.


Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (’lll be using Nginx ( as the web server/proxy and Gunicorn ( as the WSGI serverI used heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…