Hi Wesley,
Maybe it would also be helpful to point out in advance what known
behaviors (often considered as limitations) of the datastore will be
carried to the MySQL compatibility layer that Django would have to
deal with.
For example, currently using GQL counting the number of rows returned
by
On Tue, Oct 26, 2010 at 9:31 PM, James Bennett wrote:
> On Tue, Oct 26, 2010 at 7:23 PM, Alex Gaynor wrote:
>> It depends what you mean by "MySQL" compatible. If by that you mean
>> that it's importable as mysqldb and implements the exact API it should
>> work out of the box, more or less. Howe
On Tue, Oct 26, 2010 at 7:23 PM, Alex Gaynor wrote:
> It depends what you mean by "MySQL" compatible. If by that you mean
> that it's importable as mysqldb and implements the exact API it should
> work out of the box, more or less. However, if by that you mean it
> implements PEP-249 you really
On Wed, Oct 27, 2010 at 6:56 AM, wesley chun wrote:
> Dear Django developers,
>
> I got in touch with Jacob who suggested I contact you all together. As
> you may (or may not) know, at Google I/O back in May, we announced a
> hosted cloud SQL service as a new feature for our App Engine
> applicati
On Tue, Oct 26, 2010 at 6:56 PM, wesley chun wrote:
> Dear Django developers,
>
> I got in touch with Jacob who suggested I contact you all together. As
> you may (or may not) know, at Google I/O back in May, we announced a
> hosted cloud SQL service as a new feature for our App Engine
> applicati
Dear Django developers,
I got in touch with Jacob who suggested I contact you all together. As
you may (or may not) know, at Google I/O back in May, we announced a
hosted cloud SQL service as a new feature for our App Engine
application cloud-hosting platform:
http://code.google.com/appengine/bus
