On Wed, Nov 11, 2009 at 8:15 PM, Mike Malone wrote:
> Sup,
>
> I've been working on template caching (ticket #6262) with a mister
> Alex Gaynor. The patch is getting pretty stable and I think it's close
> to merge-able, so if anyone wants to take a look at what we've got and
> provide feedback: go
Sup,
I've been working on template caching (ticket #6262) with a mister
Alex Gaynor. The patch is getting pretty stable and I think it's close
to merge-able, so if anyone wants to take a look at what we've got and
provide feedback: go!
Interesting background reading for people who haven't been pa
On Thu, Nov 12, 2009 at 5:57 AM, mrts wrote:
>
> On Nov 11, 1:57 pm, Russell Keith-Magee
> wrote:
>> Also - I know you're very enthused about Git and GitHub, but Django
>> uses SVN as the canonical store for trunk and branches, and this isn't
>> likely to change in the near future.
>
> Thank you
On Thu, Nov 12, 2009 at 6:20 AM, Warren Smith wrote:
>
> If this question would be more appropriate for django-users, please
> let me know. I ask it here because I suspect that the answer to my
> question may require someone with a fairly deep understanding of the
> ORM internals.
>
> I have a l
> I find an orm usefull for 3 scenarios:
> 1. - simple object retrieval posts.objects.all()
> 2. - performance optimized object retrieval, your raw approach would
> suffice here
> 3. - generating complex queries, and reusing sql components
> When you get to complex data models, Django currently fa
If this question would be more appropriate for django-users, please
let me know. I ask it here because I suspect that the answer to my
question may require someone with a fairly deep understanding of the
ORM internals.
I have a legacy oracle database that I would like to use with the
Django ORM.
On Wed, Nov 11, 2009 at 3:57 PM, mrts wrote:
> Done, http://github.com/django-mq/django-mq .
>
> I'm willing to regularly review pull requests and add
> collaborators who are willing to do the same.
I'll keep an eye on your queue; I can easily push good patches from
there upstream to SVN.
If yo
On Nov 11, 1:57 pm, Russell Keith-Magee
wrote:
> Also - I know you're very enthused about Git and GitHub, but Django
> uses SVN as the canonical store for trunk and branches, and this isn't
> likely to change in the near future.
Thank you, but no, I'm not enthused about git and GitHub per
se :)
Johannes Dollinger wrote:
>
> Am 10.11.2009 um 17:22 schrieb Michael Glassford:
>
>> I haven't had a chance to look at the patch yet, but what you describe
>> here sounds good. I don't have any problem with you "hijacking" the
>> work.
>>
>> Did your patch deal at all with the unit tests in my
On Wed, Nov 11, 2009 at 12:00 AM, Jeremy Dunck wrote:
>
> Djangonauts,
> To help speed along development on Django, I'd like us to start
> holding regularly-scheduled sprints.
On behalf of the core team, I'd like to thank Jeremy for taking the
lead on this. Organizing an event like a sprint isn
On Wed, Nov 11, 2009 at 1:06 AM, mrts wrote:
>
> Great news! Have you discussed the workflow yet?
> I.e. will a DVCS be involved, and if yes, will there be
> a central repo for coordinating the effort?
>
> A special repo on Github would otherwise be perfect,
> but as mentioned before, we have a p
Thanks for your feedback.
I appreciate it.
I find an orm usefull for 3 scenarios:
1. - simple object retrieval posts.objects.all()
2. - performance optimized object retrieval, your raw approach would
suffice here
3. - generating complex queries, and reusing sql components
When you get to complex
12 matches
Mail list logo
