On 12/19/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
> There are quite a lot of changes in this area being considered in the
> magic-removal branch.
I figured as much. Is there any sort of estimated timeframe for the
merge of the magic-removal branch into the trunk?
> Here are a few example
> > 2) A 'columns' keyword to restrict column returns
> This already exists; look at the get_values() function:
Right idea, not quite the complete implementation. 'fields' only
applies to get_values, and the 'fields' kwarg isn't utilized by the sql
query itself. The SQL query still retrieves all
Hey Russ -
I'm still reading through your proposal, but one quick note:
On Dec 19, 2005, at 12:30 AM, Russell Keith-Magee wrote:
2) A 'columns' keyword to restrict column returns
This already exists; look at the get_values() function: http://
www.djangoproject.com/documentation/db_api/#get-
Russell Keith-Magee wrote:
> Hi all,
>
> I have a few suggestions that I think could increase the the
> capabilities and expressiveness of Django DB query syntax. The
> modifications are aimed at increasing usage of Django DB syntax (in
> preference to embedded raw SQL), and increasing the range
Hi all,
I have a few suggestions that I think could increase the the
capabilities and expressiveness of Django DB query syntax. The
modifications are aimed at increasing usage of Django DB syntax (in
preference to embedded raw SQL), and increasing the range of SQL
queries that can be expressed in
