[melbourne-pug] Introduction

[Kevin Littlejohn]

The whole design of your database will be fundamentally different  
under GAE - don't approach it like a traditional SQL database in any  
way, you'll just tie yourself in knots (personally, I think GQL is an  
abomination, because it encourages you to think you're working with  
SQL, when you're really not).

They also recommend some different layout of data for use of keys and  
entity grouping if you're doing transactions - essentially grouping  
all the data that might be referenced in a single transaction into an  
entity group, which may be orthoganol to traditional table layout.

As someone else said, if you're building for GAE, don't expect your  
code/design to be portable to anything outside GAE.  Not that there's  
anything necessarily bad about that - just worth being aware of.

KevinL

On 26/11/2008, at 09:59 , Wesley Moore wrote:

> On Wed, Nov 26, 2008 at 9:52 AM, Tennessee Leeuwenburg
> <tleeuwenburg at gmail.com> wrote:
>> Well, security and views to start with.
>
> By security I assume you mean a lack of support for fine grained  
> GRANTs?
>
>> no joins is a big one for most people.
>
> That is a big one. I'll have to look into that further.
>
> WM
> _______________________________________________
> melbourne-pug mailing list
> melbourne-pug at python.org
> http://mail.python.org/mailman/listinfo/melbourne-pug