Forgot: In the trunk the problem also exists.
2006/3/30, Daniel Bimschas <[EMAIL PROTECTED]>: > If have a model like this: > > class Article(meta.Model): > cite_key = meta.CharField(maxlength=255, primary_key=True) > ... > > where "cite_key" is a unique string used in a bibtex-file. The problem > now are the links to the edit pages created by the admin interface. > The html-code is for example: > > <a href="AAMG:05/"> > > which should link to > "http://host/bibtexapp/admin/bib/articles/AAMG:05/"; but the browser > interpretes this as "aamg:05/" because of the colons in the url. So > the thing would be to url-encode the key I think. > > I was using 0.91 before, but switched to the trunk now. > > > > > > 2006/3/30, Andy Dustman <[EMAIL PROTECTED]>: > > > > On 3/30/06, Daniel Bimschas <[EMAIL PROTECTED]> wrote: > > > > > > Hi there! > > > > > > I'm currently trying to convert an old webapp written in PHP into a > > > django-based app. The PHP-System used VARCHAR-Fields as primary keys > > > in the MySQL - DB. > > > > > > Now, if i convert the data for the new tables created by Django, I > > > have the problem that the admin interface can't edit any entries where > > > the title contains colons (":"), because the admin interface uses the > > > primary keys in the url created. > > > > > > I'm currently using Django 0.92. > > > > What sort of field (i.e. models.XXXField) are you using for your > > primary key? Sounds like maybe a SlugField? Unless you are using the > > default primary key (implicit id = models.AutoField(), which is > > INTEGER AUTO_INCREMENT)? You might then need to set primary_key in > > Meta to prevent the default PK from being created. See the model-api > > docs. > > > > (All this assumes you are using the magic-removal branch, because you > > did say 0.92.) > > > > -- > > The Pythonic Principle: Python works the way it does > > because if it didn't, it wouldn't be Python. > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
