#9706: Oracle Slugfield hardcoded to 50 chars ------------------------------------------+--------------------------------- Reporter: elealty | Owner: nobody Status: new | Milestone: Component: Database layer (models, ORM) | Version: SVN Keywords: | Stage: Unreviewed Has_patch: 0 | ------------------------------------------+--------------------------------- This has been noted a few months ago (see comments in #3588), but in trunk the situation is still the same: in the Oracle backend, slug field is created as a NVARCHAR2(50) column.
max_lenght should be onored, as in the char field. -- Ticket URL: <http://code.djangoproject.com/ticket/9706> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-updates?hl=en -~----------~----~----~----~------~----~------~--~---
