I know that FormField can be used for receiving input data. But create
a form in template is too tedious, because I need to write label for
every field myself, and I cann't auto create the label from a loop,
just like:
{% for f in form.fields %}
{{ f.formfield.verbose_name }}
{{ f
On 3/8/06, Rock <[EMAIL PROTECTED]> wrote:
It seems that no one else has any thoughts about this, so its just youand me.I read it to mean that everyone was concentrating on getting magic-removal finished. MR is all about getting the backwards incompatible changes out of the way in one big jump; on
Rock wrote:
> Finally, I agree that the name get_aggregate(s) kinda sux but I still
> haven't come up with anything better.
Sending to list this time, sorry Rock...
Throwing these into the mix:
Inventory.objects.aggregate(['AVG','MIN','MAX'],'quantity')
Inventory.objects.calculate(['AVG','MIN',
Russ,
It seems that no one else has any thoughts about this, so its just you
and me.
First I note that I agree with you about count. I am taking that out.
Next, I disagree about "average". Using the abbreviated SQLish name for
all of the functions except one is bad. Either all of the names shou
I'd especially appreciate Simon's feedback on this one as it's mostly visual.
Screenshot and summary at:
http://code.djangoproject.com/ticket/1476
Here's the summary:
I've been using a new type of edit_inline behavior for a lot of apps
here that works very well, especially for objects that have
Russell Keith-Magee wrote:
> In addition, your alternative would have 'X = article.reporter_set'
> provide useful data, but 'article.reporter_set = X' throw an exception
> - this asymmetry strikes me as much more confusing than the absence of
> strict name binding.
This is a good point, but at le
On 3/7/06, kmh <[EMAIL PROTECTED]> wrote:
>
> Thanks for the nice roundup. Votes may be in but just to clarify: my
> primary objection is that assignment is fundamentally a name-binding
> operation in Python and in this case what is bound to the name is not
> what is returned.
The fact that the
On 3/7/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Russ, I can't thank you enough for your work on this stuff. Half
> these edge cases I wouldn't have even thought of 'til they bit me in
> the ass -- I really appreciate it :)
More than welcome. Being on the other side of the world makes
Hi!
I have a ticket going for replacing the get_data_trunc_sql function
here:
http://code.djangoproject.com/ticket/1423
This has been closed with a note that MySQL's function DATE_FORMAT()
can't be used because it doesn't return a DATETIME. Putting a CAST
(DATE_FORMAT(%s,'%s') AS DATETIM
On 3/7/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> The new python site went live: http://www.python.org/
>
> And Django is on the front page. Sweet.
Although it would irk me a bit less if they dropped the silly "mega-"
prefix. :-p
--~--~-~--~~~---~--~~
You recei
The new python site went live: http://www.python.org/
And Django is on the front page. Sweet.
Luke
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to dj
hugo wrote:
>I would be +1 on this. Especially since transactions are already in
>m-r, so we won't have to worry about multiple save points playing havoc
>with our database connection.
>
I'd say -1. For it's not about database it's about what is expected
behavior. Currently I'm never sure what c
12 matches
Mail list logo
