Btw,
I found small bug on code.
Reporting here since Git repo doesn't exist yet:
http://dev.umitproject.org/projects/icm-aggregator/repository/revisions/master/entry/agents/models.py#L84
self.location_id should be self.agent_id. This passes unnoticed because
function still returns as expected. But It doesn't set correct item to the
cache so cache mechanism could not be used.
1 Nisan 2012 14:54 tarihinde orcun avsar <orc....@gmail.com> yazdı:
> Hi back,
>
> I haven't used Django Nonrel before. I went through some investigations
> over it. Actually this was because I was suspecious about Nonrel's goal to
> run native Django ORM on GAE.
>
> As you know Appengine, uses a scheme-less and non-relational database
> (for scalabilty) which requires different thinking while designing models
> and relations. Using a relational approach when designing database and
> making queries may cause a performance decrease when our data scale too
> big. This requires using Nonrel very carefully to avoid pitfalls.
>
> I think, main reason of using Nonrel is developing with existing knowledge
> from Django without learning details of GAE datastore. But this is not a
> true approach since we still need to know what Nonrel does in the
> background to maintain scalability. Same effort may be spent on
> understanding GAE datastore and using it rather than becoming dependent on
> a single tool on this platform. Second reason may be migrating an existing
> Django application into GAE without modification, which I think is not a
> very good idea too unless It's a small app.
>
> 1. I don't know if we use JOINs in existing code. Since I don't have
> code in my local machine and use my browser, I can't execute grep command
> to find out if there are any. Assuming we use JOINs on queries, Nonrel
> supports this with memory operations by running multiple queries. This is
> dangerous for big data. Alternatively, we can set denormalizations but this
> may cause redundancy.
> 2. We can use parent mechanism to run queries over mutliple Entity
> Kinds efficiently (for example to get all reports a of all nodes in a
> country). But Nonrel doesn't suport this.
>
> Anyway, I'm not in the target of changing this but I just wanted to share
> my concerns. I didn't study whole of code yet but as far as I see in the
> code these restrictions are well taken care of with redundancy.
>
> Best,
> --
> Orçun Avşar
>
Best,
--
Orçun Avşar
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Umit-devel mailing list
Umit-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/umit-devel
