If you can accomplish what you need without passing parameters, there is
certainly no requirement to do so.
Have you read: https://docs.djangoproject.com/en/stable/topics/http/urls/ ?
On Wednesday, October 7, 2015 at 12:10:54 AM UTC-4, krmane wrote:
>
> Dear all,
> I just wish to know if I must have all the parameters from my form as a
> part of the url pattern?
> I need to use only the request so was wondering if that is the case?
> I have seen tutorials and all of them come with url parameters
> I don't need a url like /articles/2013/03 etc.
> I am writing a accounting/ inventory system and don't need a blogging
> kind of application or a news room kind of stuff which Django is mostly
> known for.
> My forms will contain all the data and I can access all that in a view
> through the request object I guess?
> so a pattern like r(^setaccount'), views/account/setaccount must work.
> is this correct or do I always need to pass parameters?
> Which is the best time to use parameters apart from the request object?
> Happy hacking.
> Krishnakant.
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/db5d6795-bcbf-4f9e-97c2-b49a3efe2952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
