On Monday, June 27, 2011 7:04:09 PM UTC-7, Jim D. wrote:
So that caveat aside, I will try later to find a large data set I can run
> the query on to get an idea of what kind of performance hit the check
> entails. If anyone else has a large data set with two related tables, you
> can try it out
On Jun 27, 2011, at 5:44 PM, Michael Blume wrote:
> I see a variable saved_objects being written, but I don't see it being
> accessed -- is this to ease future features, or am I missing a code path?
Thanks good catch. This was a remnant from an earlier iteration of this patch,
in which I tried
Couple questions:
I see a variable saved_objects being written, but I don't see it being
accessed -- is this to ease future features, or am I missing a code path?
If I'm reading correctly, check_for_invalid_foreign_keys extends over all
the rows in a table. loaddata is called by syncdb and South'
On Jun 27, 2011, at 4:52 PM, Russell Keith-Magee wrote:
> Unfortunately, not much. Your test has validated that the extra code
> doesn't break anything under MyISAM, and this is certainly useful.
> However, the root problem only exists with InnoDB because of its...
> eclectic... implementation of
On Tue, Jun 28, 2011 at 7:32 AM, Michael Blume wrote:
> Just reloaded all our fixtures, and this seems to create no regressions with
> MySQL Server version: 5.0.51a-3ubuntu5.5 (Ubuntu)
> Most of our tables are backed by MyISAM, though, so I'm not sure how much
> this helps.
Unfortunately, not muc
Just reloaded all our fixtures, and this seems to create no regressions with
MySQL Server version: 5.0.51a-3ubuntu5.5 (Ubuntu)
Most of our tables are backed by MyISAM, though, so I'm not sure how much
this helps.
On Mon, Jun 27, 2011 at 4:09 PM, Michael Blume wrote:
> nitpick: I got a few compl
nitpick: I got a few complaints about trailing whitespace when I applied:
/home/mike/sqlpatch.diff:36: trailing whitespace.
/home/mike/sqlpatch.diff:42: trailing whitespace.
/home/mike/sqlpatch.diff:126: trailing whitespace.
/home/mike/sqlpatch.diff:148: trailing whitespace.
/home/mike/sqlpatc
On Mon, Jun 27, 2011 at 5:27 PM, Jim D. wrote:
> Does it work in production is a hard question for me to answer, if I
> understood your question properly. In my projects, I really only touch the
> loaddata command when I'm running tests (I guess loading data via
> initial_data.json into a producti
On Monday, June 27, 2011 3:08:03 PM UTC-7, Jacob Kaplan-Moss wrote:
>
> I left some comments on the patch on the ticket.
>
Excellent just saw those. I'll take a look.
> > I'm using django-threadedcomments on a project, which has forward
> > references in one of its test fixtures, so I'm reminde
On Mon, Jun 27, 2011 at 4:24 PM, Jim D. wrote:
> I spent some time last week and over the weekend nailing down a
> solution for https://code.djangoproject.com/ticket/3615 . This is the
> ticket about allowing forward references when loading data on the
> MySQL InnoDB backend. My patch implements t
Thank you for reviewing it.
Cheers,
Martin
On Mon, Jun 27, 2011 at 2:29 PM, Russell Keith-Magee
wrote:
> On Mon, Jun 27, 2011 at 12:58 AM, Martin Green
> wrote:
>> The unittest client currently does not allow for the testing of
>> non-formset errors. I have made a ticket for this
>> https://co
Hi all,
I spent some time last week and over the weekend nailing down a
solution for https://code.djangoproject.com/ticket/3615 . This is the
ticket about allowing forward references when loading data on the
MySQL InnoDB backend. My patch implements the proposed change
(disabling foreign key check
I reviewed:
#16358
#16355
#16359
#16353
#16316
Please look at #15829 (https://code.djangoproject.com/ticket/15829).
Thanks,
Michael Manfre
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop
On 2011-06-02, at 12:34 AM, Stephen Burrows wrote:
> Django actually already adds support for some capabilities to certain
> database backends, if I'm not mistaken - such as cascades through GFKs
> on delete.
>
> In terms of time zones, could django "assume"/ensure that the datetime
> stored in t
On Sun, Jun 26, 2011 at 12:27 AM, Stephen Burrows <
stephen.r.burr...@gmail.com> wrote:
> This is related to the recent discussion about timezone-aware datetime
> storage [1] and how django doesn't do it. Since the date filter's "c"
> argument is handled with python's datetime.isoformat() [2] time
Hi Spencer,
This sounds like a question for the Django Users group. The Django
Developers group is for matters relating to the development of the
framework itself. You can find the right group here:
http://groups.google.com/group/django-users
To answer your question though: thanks to the hard wor
This question is better suited for the Django-users group:
http://groups.google.com/group/django-users
On Mon, Jun 27, 2011 at 11:54 AM, spencer cole wrote:
> Howdy. I'm a new developer for Django. My work is starting work using
> Django 1.3, and I find I really like it as far as I've used it s
Howdy. I'm a new developer for Django. My work is starting work using
Django 1.3, and I find I really like it as far as I've used it so far.
My web hosting service, Site5, supports Django, but it's an old
version(1.1). Is there going to be any issue with what I learn and use
in Django 1.3 when I tr
Hi,
I update patch for ticket #6362 [1] to current Django trunk [2] and create
the version with stripping spaces for CharFields by default [3].
You can also find it in my fork of Official Django GIT repository for
current trunk [4] and for 1.3.X branch [5]
[1] https://code.djangoproject.com/ticke
On Mon, Jun 20, 2011 at 7:51 PM, Aymeric Augustin
wrote:
> Hello,
> Ticket #10938 [1] suggests declaring inlines in fieldsets, and was closed as
> wontfix.
> I think this ticket mixes two different things:
> (1) make it possible to *declare* inlines in
> ModelAdmin.fieldsets instead of ModelAd
On Fri, Jun 24, 2011 at 11:54 PM, stan wrote:
> This topic is discussed on the Ticket #11305 :
> https://code.djangoproject.com/ticket/11305
>
> Like many folks, I am hit by the scenario where a relative simple
> query become a design decision because my «boss» asked me : "Hey Stan,
> can you add
On Mon, Jun 27, 2011 at 12:58 AM, Martin Green
wrote:
> The unittest client currently does not allow for the testing of
> non-formset errors. I have made a ticket for this
> https://code.djangoproject.com/ticket/11603, which now has an upto
> date patch for adding it into trunk. Could I check th
Another approach is to store language in the url (useful for mobile handsets
where disabled or unsupported cookies is still an issue). Django app which
uses this method: https://bitbucket.org/carljm/django-localeurl
--
You received this message because you are subscribed to the Google Groups
On Mon, Jun 27, 2011 at 4:10 AM, Victor Hooi wrote:
> heya,
> Sorry to resuscitate an old thread, but I was just wondering if there was
> any update on this? Was somebody made the Django design czar? Or is there
> any word on the Django admin redesign front?
> (https://groups.google.com/d/topic/dj
heya,
Sorry to resuscitate an old thread, but I was just wondering if there was
any update on this? Was somebody made the Django design czar? Or is there
any word on the Django admin redesign front?
(https://groups.google.com/d/topic/django-developers/yk8m1haSF1M/discussion)
As an outsider loo
Hi,
Progress update. This week I was starting the work on the compiler
and I have at least for Django's use case most compilation things
ironed out. However it turns out that compiling AST nodes made from
scratch is a painful process as the interpreter will randomly segfault
or fail compiling wi
26 matches
Mail list logo
