#django

I had an empty slug and it saw that was empty

whats odd though

is that fors was basically doing the same thing and just showed the empty slug

i need to leave... glad that you fixed it :)

thanks man!

appreciate it!

moldy mattmcc, no

i mean in early testing i might

but the data goes into a database

and the new template is generated from that, sorta

basically the workflow is this

you create a new report instance on the site using a form

it shows up in an HTML table, with a button next to it that says "Download Excel Template"

next to that is "Upload Excel Template"

so you download it, fill it in, and upload it

that data is parsed and loaded into the other tables assocated with Report

this process might be repeated more than once though

hello everyone! I'm having an weird trouble with a login_required view...it's requiring login, but the view does not have login_required

I'm using SSL

in the test server

anyone?

it's a view that an user should access after he creates an account...so I'm pretty sure the URL DOES NOT have login_required

but you are not showing us the view, so we can't tell what else might try to force the login

sure, let me paste it

pretty dumb view...

in the local machines everything works fine

I'm using SSL on nginx and have django configured for SSL

hello django users: is there any way to explicitly ignore Meta model ordering on the queryset ?

.order_by

any wild ideas?

luzfcb: override it. that's one reason meta model overriding is generally considered not idea

ideal

pimpaa: is all access over ssl? or is some mixed?

and do you have your cookies configured to only be delivered over ssl?

yes

here is a summary of the settings

if so, then anything that takes your user out of ssl, will clear their login

SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_SSL_REDIRECT = True SESSION_COOKIE_SECURE = True CSRF_COOKIE_SECURE = True

I need no "order by" is included in a specific query

Sorry, not enough of a nginix gal to help you at that level

those are django configs

nginx is just listening at both ports, django is doing the redirection internally

but if for any reason your user goes to http___ and then gets redirected to https___ they will have lost cookies that are secure only

I'm realizing that define ordering on the model Meta class is a bad practice.

I understand that, but the link I'm generating is already poiting to https

most database engines have an implicit order

and the user haven't loogged in yet

e.g. primary key order

pimpaa: OK then I have no new ideas for you

thanks, nevertheless

the closest thing to "no order by" is explicitly order by'ing at random

basically, my question is the same of https://groups.google.com/d/msg/django-users/PD...

if Meta ordering= ['id'] is defined, the "order by" SQL is included in any query, just kills my database indexes, and make the some queries get slow

right

luzfcb: If you call order_by() with no argument, it'll clear the ordering clause.

As a general rule, I would not set Meta.ordering. Explicit is better than implicit, and all that.

well, it's still explicitly defined on your model…

mattmcc: cool. it works. Thanks.

I would happily nuke meta.ordering from this earth^^

apollo13: after my recent sufferings, can purge meta.ordering and signals from this earth

signals are useful from time to time :)

apollo13: I find ordering useful sometimes, but I suppose I could always just write a manager that automatically applies it to all querysets for the model.

Signals I abuse the hell out of.

It seems like most of the time all I do with signals is fire off Celery tasks..

ubernostrum: really? when is ordering ever useful? don't forget that this affects joins and everything

apollo13: I do a ton of stuff that wants default ordering by a date or datetime field.

ubernostrum: even over joins and annotations/aggregations?

apollo13: generally not an issue for the stuff I work with.

ok, cause it seriously can kill performance here

and remembering that one of the included tables had an ordering set is nasty imo

Like I said, if meta.ordering went away I'd just write a manager to apply ordering when I need it.

yeah, not sure though that it would be an exact replacement since it would not cover joins if done via the manager?