Thank you for kind response.
> flexible enough to handle any database-specific configuration. Would
> you be willing to code up a patch?
Yes, of course! Even I have already posted the one:
http://code.djangoproject.com/attachment/ticket/2866/ticket2866.diff .
# In the diff, I did not tested modi
[EMAIL PROTECTED] wrote:
> I want to create a bunch of Session Attributes during login. Mostly
> attrs from Active Directory that need to be available without too many
> additional calls to the LDAP server.
>
> User attempts log in -> 3rd party login backend is called -> session is
> also passed t
> No, I think you're right that we should have a mechanism in place for
> ensuring that methods like this always return results of a consistent
> type. I'm not sure whether it'd be better to do two methods or to
> return singleton tuples, though; anybody got thoughts one way or
> another?
Well, a
On 11/1/06, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
> DATABASE_ENGINE = 'sqlite'
> DATABASE_NAME = 'mydb'
> DATABASE_OPTIONS = {'charset': 'utf8'}
> ...
>
> I think this allows user-level flexibility in DB configuration, rather
> than beating out the ultimate universal default configurat
On 11/1/06, Graham King <[EMAIL PROTECTED]> wrote:
> At the moment django.core.mail does not set a Message-ID header in the
> mails it sends. SpamAssassin spots this and says INVALID_MSGID and /or
> MSGID_NO_HOST. I think the Message-ID is also used for message
> threading, and matters when you
On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote:
> > I have to say that I think you're confusing arrogance with a desire to
> > do things *RIGHT*, and a lack of time on the part of the core devs.
>
> This however is part of the issue. With rapid growth comes that lack of
> time for the founders.
> I'd just like to point out a counter-example to those arguing that the
> core developers don't listen to criticism. There was a post recently
> to django-users called "Why I'm giving up on Django" :
Agreed. I would like to point out that I am not saying the core doesn't
listen. I'm not trying
Hi all,
I'd just like to point out a counter-example to those arguing that the
core developers don't listen to criticism. There was a post recently
to django-users called "Why I'm giving up on Django" :
http://groups.google.com/group/django-users/browse_thread/thread/394701c83497e405/f85b5013b6
On 11/1/06, Yasushi Masuda <[EMAIL PROTECTED]> wrote:
>
> As in the ticket #2866, I think it would be nice if DatabaseWrapper has
> extra keyword options, which are passed to individual DB-API connection
> object constructor.
+1
I had been thinking about putting a patch together for the MySQL
ba
> What I've said here, repeatedly, is that if there's this problem, I
> want to see examples of it, because I haven't so far, and if I'm going
> to understand that there is a problem and understand where it comes
> from, I *need* to see examples. There's a big, big difference between
> that and "n
On 11/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The order_by method does not support joined tables:
> .order_by('author__username')
Hi dcramer,
This is slightly inelegant, but you can specify the SQL table name in
order_by():
order_by('myapp_authors.username')
Adrian
--
Adrian
On 10/31/06, medhat <[EMAIL PROTECTED]> wrote:
> I was trying to create a thumbnail from an ImageField when the object
> is saved. I tried different things but none of them worked the way I
> wanted. Then I thought of using the post_save signal to do it only to
> discover that this signal is sent
On 11/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> The order_by method does not support joined tables:
> .order_by('author__username')
Yes, this is ticket #2076: http://code.djangoproject.com/ticket/2076
Until someone figures it out, a workaround would be to do
.extra(tables=['auth_user
On 11/2/06, wam <[EMAIL PROTECTED]> wrote:
> I'd like to propose that this decision be reconsidered. I hope this
> isn't too much of a paraphrase, but it seems that the resolution of 443
> boiled down that -00-00 time/date stamps are a MySQL botch and not
> something Django should work around.
On 10/31/06, medhat <[EMAIL PROTECTED]> wrote:
> Should the post_save signal be moved to after the files are saved, or
> can we have another signal that is fired then?
Hm. Personally, I could go either way on this, but I think I'd prefer
having a new signal, because that gives maximum flexibility
On 10/31/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I propose to split the functionality into two separate methods,
> valueslist() and valuetupels(). valueslist() would only allow to
> pass in a single attribute name.
>
> valuelist(attname) --> always yields single values
>e.g., list(val
The order_by method does not support joined tables:
.order_by('author__username')
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@go
As in the ticket #2866, I think it would be nice if DatabaseWrapper has
extra keyword options, which are passed to individual DB-API connection
object constructor.
For example, MySQLdb allows "charset" option that can be used to
determine default_character_set of a connection. Pysqlite has
are ti
Hi,
I was trying to create a thumbnail from an ImageField when the object
is saved. I tried different things but none of them worked the way I
wanted. Then I thought of using the post_save signal to do it only to
discover that this signal is sent after the object itself is saved but
before all th
> well, then I do. I´m scared away. why? exactly because of what james
> is writing here.
> it seems that noone except the "core developers" are allowed to
> criticize django - whenever something like this comes up on the list,
> there´s someone who fights the arguments tooth and nail. there´s no
> The problem of long waiting patches is not unique to Django, it's a
> common thing in Open Source. It's inevitable in any project where there
> are less reviewers than contributors because people's time is limited.
> Everybody understands it but the huge difference here is that people
> sho
Graham King wrote:
> Does this sound sane ? If so I will submit a proper patch.
I don't think anyone would turn down the submitting of a patch. I
would suggest at least opening a ticket.
--~--~-~--~~~---~--~~
You received this message because you are subscrib
I think you raise a valid point. There are valid use cases for both
methods.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@google
James Bennett wrote:
> I would like to see examples of this; I have a pretty comprehensive
> set of ego searches and tag subscriptions for Django-related postings,
> and I don't get the "Django is closed, don't bother trying to get
> involved" vibe as much as you apparently do.
Smart people don't
Hey all --
So we're getting started on the Django/Oracle sprint in Boulder. Just for
today, please refrain from any checkins to the django.db package while we work
out on our branch.
Wish us luck, and feel free to join us in #django if you'd like to follow along!
Jacob
--~--~-~--~--
On Sat, 2006-11-04 at 07:34 -0800, Guillem wrote:
> Hello,
>
> I would really like to use inheritance in my models. In 0.95 this
> doesn't work. According to
> http://code.djangoproject.com/wiki/ModelInheritance there is some work
> underway in supporting it. Has some progress been made, if not,
Hello,
I would really like to use inheritance in my models. In 0.95 this
doesn't work. According to
http://code.djangoproject.com/wiki/ModelInheritance there is some work
underway in supporting it. Has some progress been made, if not, why?
Can I help? As far as I can see developers need to agree
Malcolm Tredinnick wrote:
> On Fri, 2006-11-03 at 22:19 +, Rob Hudson wrote:
>> Jacob Kaplan-Moss wrote:
>>> Try this::
>>>
>>> from innovate.innovation.models import Innovation
>>> from django.contrib.contenttypes.models import ContentType
>>>
>>> i = Innovation.objects.get(id=1)
I miss the "Week In Review" blog posts from Adrian but surely he's not
writting those to have more time for coding :)
On 11/4/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> And to clarify regarding Trac in particular: that's not really a
> Django issue, it's a server maintenance issue. "We're w
> So far as I can tell, our biggest long-term management problem right
> now is not one of scaring developers away, it's one of keeping track
> of all the people who want to get involved and all the things they
> want to do. You haven't yet provided an example to the contrary.
well, then I do. I´
On Fri, 2006-11-03 at 22:19 +, Rob Hudson wrote:
> Jacob Kaplan-Moss wrote:
> > Try this::
> >
> > from innovate.innovation.models import Innovation
> > from django.contrib.contenttypes.models import ContentType
> >
> > i = Innovation.objects.get(id=1)
> > ct = ContentType.obje
On 11/3/06, iain duncan <[EMAIL PROTECTED]> wrote:
> Does there exist somewhere a full reference to every template variable
> available to the admin templates? I think this would be very useful. I
> looked but couldn't find one, so maybe it's just hiding somewhere. Would
> be good to know for inst
On 11/4/06, iain duncan <[EMAIL PROTECTED]> wrote:
> Every single comparison of Gears to Django I have read say something to
> the effect of "Gears is more community based". I think that's pretty
> clear if you read between the lines. And part of what I'm going on about
> is addressed in your blog
33 matches
Mail list logo
