[socal-piggies] Seeks guidance: Python 2.7, XML, SQL, ...on GAE

[Grig Gheorghiu]

I concur with Michael. If you want to use GAE, you might as well use
their 'infinitely scalable' datastore, which is basically Google's
BigTable. Why restrict yourself to MySQL? The learning curve may be a
bit steep but it's worth it.

However, as Michael says, make sure you have a strategy for exporting
that data somehow. It won't be easily importable into a relational DB,
but at least you should have it around for disaster recovery purposes.

Grig

On Thu, Jan 5, 2012 at 5:38 PM, Michael Elkins <me at sigpipe.org> wrote:
> On Thu, Jan 05, 2012 at 04:45:37PM -0800, Daniel Stewart wrote:
>>
>> I'm currently stuck trying to parse the contents of a single RSS feed,
>> from an RDF Schema, iso-8859-1 encoded, XML document, at single known
>> URL, using the cElementTree module; To then store this parsed data, in
>> a single SQL database, via the MySQLdb library, at an initial rate of
>> 1x daily on, wait for it...
>>
>> Google App Engine (GAE).
>
>
> You may want to investigate GAE's data store before you proceed.  You will
> not be able to use mysqldb, because GAE has it's own datastore with a
> different API.  I haven't looked at the state of open-source
> reimplementations (see the wiki link below), but one thing to consider is
> what you will do if you need to migrate off GAE in the future and not be
> locked in.
>
> http://code.google.com/appengine/docs/python/gettingstarted/usingdatastore.html
>
> http://en.wikipedia.org/wiki/Google_App_Engine#Portability_concerns
>
>
> _______________________________________________
> socal-piggies mailing list
> socal-piggies at lists.idyll.org
> http://lists.idyll.org/listinfo/socal-piggies