StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow should I convert this long and complex PHP style URL query string to a Django url?
primarykey
Id
2039054
data
AcceptedAnswerId
2039079
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-01-10T23:09:43.357
FavoriteCount
0
LastActivityDate
2010-01-10T23:18:57.750
LastEditDate
LastEditorUserId
0
OwnerUserId
92448
ParentId
0
PostTypeId
1
Score
3
ViewCount
484
LastEditorDisplayName
text
Body
I'm converting a small PHP application to Django. One section has a long query string, indicating how a widget is to be displayed. There are a few required parameters and several optional ones. The current urls read like: <pre><code>app.php?id=102030&size=large&auto=0&bw=1&extra=1 </code></pre> The id and size are required, but auto, bw and extra are optional. I use defaults if they're not specified. My first idea was to make a django URL pattern with the required info, id and size: <pre><code>url(r'^/app/(P?<id>)\d+/(P?<size>)\w+$',app.project.views.widget,name='swidget') </code></pre> The optional parameters would then be a query string, like <pre><code>/app/102030/large?auto=0&bw=1&extra=0 </code></pre> Is it a common practice to mix GET parameters with parameters defined in the URL conf in Django? Or should I make it like <pre><code>url(r'^/app/(P?<id>)\d+/(P?<size>)\w+/(P?<auto>)\d/(P?<bw>)\d/(P?<extra>)\d[/]?,'app.project.views.widget,name='swidget') #so it would look like: /app/102030/large/0/1/0/ </code></pre> Any suggestions about best practices or issues to keep in mind with either style are appreciated!
Tags
<python><django><url><url-routing>
Title
How should I convert this long and complex PHP style URL query string to a Django url?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJAL
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow should I convert this long and complex PHP style URL query string to a Django url?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POHow should I convert this long and complex PHP style URL query string to a Django url?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI also found this question http://stackoverflow.com/questions/150505/django-capturing-url-parameters-in-request-get which covers similar issues.
 singulars
 PostPostId
 POHow should I convert this long and complex PHP style URL query string to a Django url?
 UserUserId
 USJAL

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.