You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have made it unique now in the models.py file. It would make sense for it to be unique, as a slug is a lot easier on the eyes than someone seeing numbers all over the place and questioning what is being referred.
Although I'm not sure we even need a slug on Facility, I just checked and it isn't used ANYWHERE in the code. I will do some testing to see what commenting this out affects.
That's what I thought. There is no facility page where a slug would be useful. We might as well drop it. Just wanted to confirm.
-----Original Message-----
From: Tyrel Souza [mailto:reply@reply.github.com]
Sent: Wednesday, June 13, 2012 10:46 AM
To: Christian Spanring
Subject: Re: [bostonparks] Slug on model class Facility is not unique (#96)
Although I'm not sure we even need a slug on Facility, I just checked and it isn't used ANYWHERE in the code. I will do some testing to see what commenting this out affects.
Reply to this email directly or view it on GitHub: #96 (comment)
Please be advised that the Massachusetts Secretary of State considers e-mail to be a public record, and therefore subject to the Massachusetts Public Records Law, M.G.L. c. 66 § 10.
Does it need to be unique?
The text was updated successfully, but these errors were encountered: