Thanks.
So when i was student, i used to do joins programatically, that was 7 years
ago , and my teacher blame me how bad that design was.
Now thats gonna be a useful in NoSQL dbs
:).
On Mon, Oct 24, 2011 at 7:40 AM, howesc wrote:
> it is very much a mindset. joins are expensive no matter wh
it is very much a mindset. joins are expensive no matter what system you
use (well they are not free, though still very fast on a relational system),
so when they build GAE which is supposed to be optimized for web page views,
they disallowed joins. i have a love/hate relationship with it!
Oh Hell, To join programatically!! Ewww!!
Finally bad (relational) database designs are gonna look good in GAE,,
I think i am gonna brainwash myself and Jump onto NoSQL Bandwagon too
On Sun, Oct 23, 2011 at 5:46 AM, howesc wrote:
> the default datastore for GAE is a NOSQL system of key-value pa
the default datastore for GAE is a NOSQL system of key-value pairs. it does
not have the full concept of referenced tables, and does not support a join
operation.
your options are to flatten your schema, putting all the necessary data in a
single record rather than splitting it into many table
So because of join operation , it have problem with DAL over GAE right?
What is recommend work around for one to many relationship ?
Just use single table?
That gonna be awful..
On 10/23/11, Phyo Arkar wrote:
> Anyone get this problem?
>
> I am using web2py 1.98.2 on GAE .
>
> WHat is the work
Anyone get this problem?
I am using web2py 1.98.2 on GAE .
WHat is the work around for it?
On 10/23/11, Phyo Arkar wrote:
> def get_totals():
> response.generic_patterns = ['json']
> query=(db.item.id==db.sale.id_items)
> total_price = 0
> total_cost = 0
> total_it
6 matches
Mail list logo
