Thanks carl for updating me about this fix.
I was using 1.3-beta-1 version of django. When i run it with latest
trunk version it works fine.
Thanks,
Rahul Priyadarshi
On Feb 24, 9:16 am, Carl Meyer wrote:
> Hi Rahul,
>
> On Feb 21, 12:56 am, Rahul
Hi Rahul,
On Feb 21, 12:56 am, Rahul wrote:
> When i ran the test cases ( "modeltests/delete/
> test_inheritance_cascade_up" ) which were doing cascade up for
> inherited models, it failed for DB2 cause of the fact that DB2 doesn't
> support initial deferred
I agree that this makes a lot of sense for 1.4.
Probably the most common use case is going to be separating classes of
emails (mass-mails (mailchimp or constant contact), transactional
(amazon ses or your provider's mailserver), backend admin
notifications (server sendmail or local mail spool),
On Thu, Feb 24, 2011 at 8:44 AM, Paul wrote:
> Dear all,
>
> allow me to quickly introduce myself, my name is Paul, I'm a PhD
> student from Germany and am playing around with django for mere joy
> (procrastination).
>
> I have a quick question on why ticket #15352 (
Dear all,
allow me to quickly introduce myself, my name is Paul, I'm a PhD
student from Germany and am playing around with django for mere joy
(procrastination).
I have a quick question on why ticket #15352 (
http://code.djangoproject.com/ticket/15352
) was closed?
It just took me a fair
On Thu, Feb 24, 2011 at 1:44 AM, Luke Plant wrote:
> On Tue, 2011-02-22 at 19:02 -0600, Niran Babalola wrote:
>> Multiple databases and caches can currently be configured in one's
>> settings file. It'd be nice if the same could be done with email
>> connections. For
Well writing a middleware in my app or decorating all views seems a little
hacky/unclean to me too.
In our specific use case, the django CMS the graceful degrading is done
through the admin, our so called frontend editing is heavily javascript and
AJAX base, without HTML forms. therefore we
On Wed, 2011-02-23 at 05:07 -0800, Jonas Obrist wrote:
> I beg to differ luke.
>
>
> Most of our AJAX POSTs we do are actually not a 'form'. Because we
> usually submit forms with 'normal' POST requests.
I was suggesting that normally you would encounter at least one normal
form before doing
On Wed, Feb 23, 2011 at 11:44 AM, Luke Plant wrote:
> Is it not possible to do this already, by writing your own backend that
> splits up e-mails as you see fit?
Yes, but it'd be nice if the get_connection arguments for each
connection type could be easily referenced by
On Tue, 2011-02-22 at 19:02 -0600, Niran Babalola wrote:
> Multiple databases and caches can currently be configured in one's
> settings file. It'd be nice if the same could be done with email
> connections. For example, Amazon's SES starts out new users with a low
> quota that they gradually
On Feb 22, 11:22 am, Russell Keith-Magee
wrote:
> 2) Directing people who are inclined to be altruistic to the right place.
For Firefox bugs, each patch can be flagged as follows:
Request a review from anyone: review=?
Request a review from someone specific:
+1
On Tue, Feb 22, 2011 at 8:39 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Wed, Feb 23, 2011 at 9:02 AM, Niran Babalola wrote:
> > Multiple databases and caches can currently be configured in one's
> > settings file. It'd be nice if the same could be done
I beg to differ luke.
Most of our AJAX POSTs we do are actually not a 'form'. Because we usually
submit forms with 'normal' POST requests.
What would be so terrible in just setting the cookie always?
Jonas
--
You received this message because you are subscribed to the Google Groups
"Django
Hey Tim
Thanks for the report! I don't think this is a bug; you might want to read the
documentation a little more closely.
http://docs.djangoproject.com/en/dev/ref/django-admin/#testserver-fixture-fixture
testserver runs the Django development server using data from the passed
fixtures. This
On Wed, Feb 23, 2011 at 8:24 PM, Jonathan S wrote:
> Aparently, there are several semicolons missing at several places:
>
> django/contrib/admin/templates/admin/edit_inline/tabular.html lines
> 90, 94 and 124
>
Hi,
I'm new to Django and Python but I think I've found a bug with the
testserver.
What happened is that Django wouldn't let me log in to my newly-
created superuser account and kept saying "Please enter a correct
username and password" despite the fact that I was 100% sure the
information was
Aparently, there are several semicolons missing at several places:
django/contrib/admin/templates/admin/edit_inline/tabular.html lines
90, 94 and 124
django/contrib/admin/templates/admin/edit_inline/stacked.html lines
45, 48 and 78
Of course, this really is a minor issue, but easy enough to
Hi Django admin developers,
Can you please insert a semi-colon in the following file, behind line
90?
django/contrib/admin/templates/admin/edit_inline/tabular.html
var updateSelectFilter = function() {
// If any SelectFilter widgets are a part of the new form,
18 matches
Mail list logo