#django

how would i want to try and store a users last search requests from a page, say they do some filtering on a listing page, click for details, then go back to the list page - I want the most recent filtering to be applied

session ?

fission6: ^

and how would i store that kind of info in the session framework

you can store anything that's json serializable

You can store anything in sessions.

i am asking how would i want to store the last search info, what would be your approach

fission6: how are the search parameter passed to the page? GET parameters?

yes

then in your view, you do something like: request.session['search_param_1'] = request.GET.get('search_param_1')

I'd do something like request.session['my_session_key'] = request.GET.dict()

knbk: you're right, sorry, missed those two lines.

ya, and then wouldn't i want the reverse to actually use the settings

(settings = search params)

or maybe some kind of redirect

fission6: Then you do "reverse" when page is loaded "second" time, if request.GET.get('search_param_1') is empty, you will see if you have a value in session etc...

ok will review

could i also just do a redirect to a new url with the querystring and clear the session setting

fission6: if you're doing a redirect you could save the original query string, request.META.get('QUERY_STRING', '')

in the session right?

yeah, in the session

i was thinking that and if its a session variable the clear that key and redirect to the value

would be pretty simple to acheive the idea of, show the last filtering

morning

Moin

hi folks, I have a really strange problem... https://dpaste.de/m9MS it literally says that it has tried the path, yet apparently it was not found (matched)

for instance http://localhost:8000/app/ works

I’m really confused about Django ORM foreign key and relational database schema design. If i take this example http://www.1keydata.com/sql/sql-foreign-key.html and do python manage.py inspectdb it will create an Orders model class with an field customer_SID for our foreign key.

However in Django it seems like that foreign key should be in the Customer class? For example http://www.yilmazhuseyin.com/blog/dev/django-or... shows that Employee has a field department that’s a foreign key to access department related objects.

from the second example it just seems like the foreign key field should be in the Customer class not the Orders class?

the way it's done in SQL and django ORM seems reversed which confuses me

if you were going to design a relationship between the two and write the models, would you write the foreign key field in the Customer or the Orders class?

or i guess it depends on what you're trying to access first?

Frenchiie: An Order can have a single Customer, so the foreign key would go in the Order class. This creates a field in the order table that can hold a reference to a single customer row

so that's just like the customer_SID field

Just like an Employee belongs to a single Department, so the ForeignKey would go in the Employee class

knbk: yeah i guess that makes sense

i'm just curious if an Employee were to belong to multiple department what would be the cost of doing a reverse lookup

if an Employee belongs to multiple Departments, the relation is wrong to begin with

the employee table has a single column that refers to a department, so an employee can only relate to one department at a time

knbk: not sure i follow. The department field in Employee doesn't have OneToOneField

knbk: why can't an Employee belong to multiple Departments?

Frenchiie: That means a department can have multiple employees, but an employee cannot belong to multiple departments