Re: Google App Engine

On Apr 8, 2008, at 9:12 AM, Robert Walker wrote: I don't know if it would be possible to integrate EOF and such a data store, as EOF is very tight to the relational model, without doing some heavy trickery Speaking of that, why do we continue the "Cargo Cult" of the relational database?

Re: Google App Engine

Miguel Arroz wrote: FYI: http://code.google.com/appengine/docs/ whatisgoogleappengine.html I bet Mike can't write an adaptor for the Datastore in a weekend... ;) He can't, he's too busy writing is own operating system: MikeOS 1.3.0 Released ;-) -- Francis

Re: Google App Engine

To quote Chuck... From: Chuck Hill <[EMAIL PROTECTED]> Date: 13 March 2008 9:37:05 AM Sounds suspiciously like "I can't"... ;-) On 09/04/2008, at 1:53 AM, Mike Schrag wrote: I actually looked at this ... I'm not sure if you can access the datastore outside of the python API's running in the

Re: Google App Engine

One of our suppliers used this DB and it was, to use a technical term, a bag of crap. That was a few years back now, so it may have moved on a bit, but it's one of those things filed under "avoid at all costs" in my brain. Exactly why I made it very clear that I don't have any details on

Re: Google App Engine

One of our suppliers used this DB and it was, to use a technical term, a bag of crap. That was a few years back now, so it may have moved on a bit, but it's one of those things filed under "avoid at all costs" in my brain. To me relational = reliable. It's a bit like EOF vs Ruby on Rails.

Re: Google App Engine

I do agree, I hate relational DBs. The problem is that I still didn't find any other persistent store that: 1) Can scale and handle high load (in a real environment, not just on the spec sheet); 2) Is affordable/free; 3) Integrates well with powerful frameworks like WO. http://www.

Re: Google App Engine

Hi! On 2008/04/08, at 17:12, Robert Walker wrote: Speaking of that, why do we continue the "Cargo Cult" of the relational database? Isn't it about time to move past them, and begin moving to persistent storage that makes sense in the modern age of objects? That's all I'll say on the subje

Re: Google App Engine

I don't know if it would be possible to integrate EOF and such a data store, as EOF is very tight to the relational model, without doing some heavy trickery Speaking of that, why do we continue the "Cargo Cult" of the relational database? Isn't it about time to move past them, and begin

Re: Google App Engine

Hi! Of course I was! :) I don't know if it would be possible to integrate EOF and such a data store, as EOF is very tight to the relational model, without doing some heavy trickery (ie, bugs, instability, limitations, etc). And there's also the problem of not being able to access it ou

Re: Google App Engine

. but then i think you were only semi-serious ;) On Apr 8, 2008, at 11:53 AM, Mike Schrag wrote: I actually looked at this ... I'm not sure if you can access the datastore outside of the python API's running in the cluster. Amazon's is a possibility also, but the query capability is ver

Re: Google App Engine

I actually looked at this ... I'm not sure if you can access the datastore outside of the python API's running in the cluster. Amazon's is a possibility also, but the query capability is very limited, and joins would have to be implemented inside the adaptor. Google's at least appears to

Google App Engine

Hi! FYI: http://code.google.com/appengine/docs/whatisgoogleappengine.html I bet Mike can't write an adaptor for the Datastore in a weekend... ;) Yours Miguel Arroz Miguel Arroz http://www.terminalapp.net http://www.ipragma.com smime.p7s Description: S/MIME cryptographic signatur