Since you're at Berkeley, stop by the Graduate School of Journalism some
time to see the Django sites we run and meet the devs (look me up). Would
also be interested in campus Django meetings (any alternative to the
relentless Drupal push on campus :).
./s
--
You received this message because
On Wed, Sep 28, 2011 at 3:36 AM, Paul McMillan wrote:
> I'm Paul, one of the core devs for Django. I'm curious which class
> you're enrolled in and what your requirements are. I'm always excited
> to see new people looking to get involved in the project, and I happen
> to be VERY local.
Hi Paul &
Hi Jamin,
I'm Paul, one of the core devs for Django. I'm curious which class
you're enrolled in and what your requirements are. I'm always excited
to see new people looking to get involved in the project, and I happen
to be VERY local. If you wanted to meet up some evening in one of the
libraries
Alec,
I'm glad you're excited about this issue, but let's keep discussion of
the installation issue on the other thread (and/or the ticket
tracker). It would be best if we didn't go tasking new volunteers with
big projects the community hasn't agreed on.
The ticket tracker, and the issues there,
Am 27.09.2011 um 05:18 schrieb Luke Plant:
> On 27/09/11 03:23, Alex Gaynor wrote:
>
>> I'm not a fan of this, for a few reasons, firstly: because it feels
>> wrong for a QuerySet to execute multiple queries. This isn't a deal
>> breaker, just something that struck my conceptually initially. S
Hallöchen,
some non-relational databases (e.g. MongoDB) have support for
arbitrarily nested objects. To make queries that "reach" into these
sub-objects, the Django-nonrel developers find it appealing to use JOIN
syntax. For instance, if you had this person in your database
{'name': 'Bob',
I'd just like to chime in to say this should definitely be part of
core - it's a common requirement, and whilst it could be a third party
app, it certainly feels much more at home in core.
On Sep 27, 1:13 pm, Luke Plant wrote:
> For me, QuerySet is at a level of abstraction where I don't think it
Hi Alex,
Just replying to your other objections, now I've had some time to think
about them:
On 27/09/11 03:23, Alex Gaynor wrote:
> I'm not a fan of this, for a few reasons, firstly: because it feels
> wrong for a QuerySet to execute multiple queries. This isn't a deal
> breaker, just somethin
On 27 sep, 05:18, Luke Plant wrote:
> On 27/09/11 03:23, Alex Gaynor wrote:
>
> Would you like to share your solution? I found it pretty difficult to
> come up with anything that:
>
> 1) could be done on a per-query basis and
> 2) didn't require changes to the code that would use the QuerySet
>
