Johannes Dollinger wrote:
>
> Am 10.11.2009 um 17:22 schrieb Michael Glassford:
>
>> I haven't had a chance to look at the patch yet, but what you describe
>> here sounds good. I don't have any problem with you "hijacking" the
>> work.
>>
I haven't had a chance to look at the patch yet, but what you describe
here sounds good. I don't have any problem with you "hijacking" the work.
Did your patch deal at all with the unit tests in my patch that
intentionally failed to expose things that weren't working right yet?
Mike
Johannes
Jani Tiainen wrote:
> Michael Glassford kirjoitti:
>>
>> Alex Gaynor wrote:
>>
>>> Can you upload it with a .diff extension so we can get proper code
>>> highlighting on trac.
>>>
>>> Alex
>>>
>> Sorry. Done.
>
>
Alex Gaynor wrote:
> Can you upload it with a .diff extension so we can get proper code
> highlighting on trac.
>
> Alex
>
Sorry. Done.
Mike
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
Jani Tiainen wrote:
> Michael Glassford kirjoitti:
>>
>> Jani Tiainen wrote:
>>> Is there anyone working for this ticket?
>>>
>>> There seemed to be few patches but then a silence.
>>>
>>> I would be interested in to help/implement th
Jani Tiainen wrote:
> Is there anyone working for this ticket?
>
> There seemed to be few patches but then a silence.
>
> I would be interested in to help/implement that feature since it's very
> highly needed feature in our own code.
>
I am. The silence is due to a couple of problems I've
Jacob Kaplan-Moss wrote:
> Hi folks --
>
> Y'know, there's quite a bit of bike-shedding going on in this
> discussion, and not a whole lot of code writing. Remember that our
> general policy is that whoever builds the shed gets to paint it; y'all
> might want to spend some of this energy actually
Martin Maney wrote:
> On Sat, Aug 15, 2009 at 10:45:44AM -0700, hcarvalhoalves wrote:
>> ForeignKey(..., propagate_on_delete=True)
>> CASCADE
>>
>> ForeignKey(..., propagate_on_delete=False, null=False)
>> RESTRICT
>>
>> ForeignKey(..., propagate_on_delete=False, null=True)
>> SET NULL
>>
>> Forei
Michael Glassford wrote:
>
>
> hcarvalhoalves wrote:
>> On Aug 14, 11:48 pm, Russell Keith-Magee
>>
>> wrote:
>>> On Sat, Aug 15, 2009 at 8:09 AM,
>>> hcarvalhoalves
>>> wrote:
>>>
>>>> On Aug 13, 9:30 am, Ru
hcarvalhoalves wrote:
> On Aug 14, 11:48 pm, Russell Keith-Magee
>
> wrote:
>> On Sat, Aug 15, 2009 at 8:09 AM,
>> hcarvalhoalves wrote:
>>
>>> On Aug 13, 9:30 am, Russell Keith-Magee
>>>
>>> wrote:
>>>> On Thu, Aug 13, 2
Russell Keith-Magee wrote:
> On Sat, Aug 15, 2009 at 10:57 AM, Michael Glassford
> wrote:
>> Russell Keith-Magee wrote:
>>> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
>>> wrote:
>>>> On Aug 13, 9:30 am, Russell Keith-Magee
>>>>
Russell Keith-Magee wrote:
> On Sat, Aug 15, 2009 at 8:09 AM, hcarvalhoalves
> wrote:
>> On Aug 13, 9:30 am, Russell Keith-Magee
>> wrote:
>>> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
>>> wrote:
>>>
>>> Secondly: I'm sen
Russell Keith-Magee wrote:
> On Fri, Aug 14, 2009 at 12:06 AM, Michael Glassford
> wrote:
>> Russell Keith-Magee wrote:
>>> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
>>> wrote:
>>>> http://code.djangoproject.com/ticket/7539 suggests a way to a
Russell Keith-Magee wrote:
> On Thu, Aug 13, 2009 at 12:04 AM, Michael Glassford
> wrote:
>> http://code.djangoproject.com/ticket/7539 suggests a way to add On
>> Delete and On Update support to Django foreign key fields, and includes
>> a patch that implements the su
Previously accidentally posted to the Django users group instead of
here. Sorry!
http://code.djangoproject.com/ticket/7539 suggests a way to add On
Delete and On Update support to Django foreign key fields, and includes
a patch that implements the suggestions. At the time I submitted it,
getti
Russell Keith-Magee wrote:
> On Fri, Feb 20, 2009 at 1:49 AM, Michael Glassford
> wrote:
>> Just yesterday I updated the patch attached to
>> http://code.djangoproject.com/ticket/7539 so that it will apply against
>> the current version of Django (the previous pa
Just yesterday I updated the patch attached to
http://code.djangoproject.com/ticket/7539 so that it will apply against
the current version of Django (the previous patch required Django 0.96).
What are the chances of some form of this patch being included in one of
the next couple of versions o
Don't forget http://code.djangoproject.com/ticket/7539. The patch is
old--it's for Django 0.96--so it needs to be updated. Hopefully I'll
manage to do this in the next week or two as we start moving our project
from 0.96 to 1.0.x. But it to handles ON CASCADE DELETE / RESTRICT
SET NULL behavio
alex finn wrote:
> Hi Mike,
>
> thanks, this really helps and makes complete sense.
> In this case, could it be a feature request for django to implement
> bidirectional delete for related models in OneToOne case?
I'm not officially connected to the Django project in any way, so you
can make su
alex finn wrote:
> Hi Everybody,
>
> I need some assistance on django's OneToOne mapping implementation.
> Several days ago I started a discussion in django-users but didn't get
> too much of feedback :(
> Here it is:
> http://groups.google.com/group/django-users/browse_thread/thread/8b30b3bdc15
Luke Plant wrote:
> On Friday 20 June 2008 23:40:43 Michael Glassford wrote:
>> Django builds a list of all the objects that are foreign keyed to
>> the one you are deleting and deletes those first, so it bypasses
>> any ON DELETE clauses. I assume this is what you're
Django builds a list of all the objects that are foreign keyed to the
one you are deleting and deletes those first, so it bypasses any ON
DELETE clauses. I assume this is what you're seeing.
I'm preparing to propose a patch that will add ON DELETE and ON UPDATE
support to Django (so that you c
Russell Keith-Magee wrote:
> On Thu, Jun 19, 2008 at 11:00 PM, Michael Glassford
> <[EMAIL PROTECTED]> wrote:
>> Now for one of the reasons that I've been trying to get the Django unit
>> tests running: I'm interested in submitting a patch that adds some ON
Marc Fargas wrote:
> El jue, 19-06-2008 a las 11:00 -0400, Michael Glassford escribió:
>> * If settings.DATABASE_HANDLES_ON_DELETE=True, the SQL that is generated
>> by manage.py contains ON DELETE clauses where on_delete= is
>> specified.
>>
>> * If setting
Now for one of the reasons that I've been trying to get the Django unit
tests running: I'm interested in submitting a patch that adds some ON
DELETE and ON UPDATE support in Django. But first, I want to see what
interest there is in such a patch. There have been a number of tickets
about this
Django with this patch for a long time but never
> got around to submitting it.
>
> Pim.
>
>
>
> Michael Glassford wrote:
>> I'm still trying to run the Django unit tests for the first time. I've
>> worked through most of the errors--all of them so far
I'm still trying to run the Django unit tests for the first time. I've
worked through most of the errors--all of them so far proved to be
caused by the MySQL/InnoDB ordering problem when deserializing objects
that I asked about in another thread. However, I have one more set of
errors that app
Russell Keith-Magee wrote:
> On Thu, Jun 19, 2008 at 3:44 AM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>
>>> from what that says I'd guess you are using the InnoDB MySQL storage
>>> backend,
>> Right you are. That limitation is a bit of a pain.
>
Ramiro Morales wrote:
> On Wed, Jun 18, 2008 at 3:51 PM, Michael Glassford <[EMAIL PROTECTED]> wrote:
>> I'm trying to run the Django unit tests for the first time using
>> runtests.py and I'm getting a lot of errors like this:
[snip]
> This could be relate
I'm trying to run the Django unit tests for the first time using
runtests.py and I'm getting a lot of errors like this:
> Problem installing fixture
'/develop/django/tests/regressiontests/views/fixtures/testdata.json':
Traceback (most recent call last):
> File
"/Library/Frameworks/Python
30 matches
Mail list logo
