Changes between Initial Version and Version 1 of Ticket #22877


Ignore:
Timestamp:
Jun 23, 2014, 4:48:11 AM (10 years ago)
Author:
Shai Berger
Comment:

Hi,

When segmentation faults are involved, we need to know many more details in order to be able to verify and take action. In particular:

Platform (that is, which operating system are you using?) Exact Python version; Exact Django version; Database backend; Exact version of database library; Anything else of this kind that might seem relevant.

We know about segmentation faults with Python 3 (any version of Python 3), using Oracle and cx_Oracle 5.1.2 on Linux with Django>=1.5. This was a bug in cx_Oracle that was solved in 5.1.3, released recently. If your situation is different, we'll be very interested to learn about it.

Thanks, Shai.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #22877

    • Property Cc Shai Berger added
    • Property Component Core (Other) → Database layer (models, ORM)

  • Ticket #22877 – Description

    initial v1  
    11Hi,
    22Lets take the following models:
     3{{{#!python
    34#models.py
    45class Item()
    … …  
    1112        UserProfile, verbose_name=_('user profile'), related_name='user_profile_appreciation'
    1213    )
     14}}}
    1315
    14 ####
    1516With a populated database, the following line trigger a Segmentation fault:
     17{{{#!python
    1618#Main.py
    1719if Item.objects.prefetch_related('item_appreciation'):
    1820    print 'lol'
    1921
     22}}}
    2023
    2124
    2225
    23 
Back to Top