#django

1.5.x should be fine. Though obviously upgrading to PG 9.x would be ideal.

yeah, i'd love that

but, you know ... it's not possible right now

unless you are using some custom queries

the datbase for django should upgrade cleanly

to newer postgresql.

Well, ugprading from 8.2 to 9.anything won't be trivial.

my hands are tied here. there are over 40k servers and they all have the same base installation. no touching.

We're talking about versions that are eight years apart.

behelit: Something to keep in mind, once Django 1.7 is released in May-June, 1.5 won't be supported anymore.

mattmcc: i see. i'll make sure to disappear from the face of the earth before may then.

40k servers holy moly

aidan: they're not all running django. only like ten :)

Property.objects.filter(reportschedule__next_due__range=(start, end)) .... that returns multiple property records because it's a M21 relationship. Can I just run distinct to get only the properties or is there a better way?

upgrading to PG 9.3 and Django 1.6 will pay off so well

I speak from experience :)

aidan: Property.objects.filter(reportschedule__in=ReportSchedule.objects.filter(next_due__range=(start, end)).distinct()) ?

ok, i might be able to go to 8.4

i'll know tomorrow

mattmcc, daveb: thanks a lot for your time

FunkyBob: ah nice

hi, why would the union operator on two query sets duplicate an object?

am I misunderstanding what the operator does?

there's a union operator? :)

'|'

QS + QS ?

QS | QS

JDShu: It doesn't do a union, it combines the criteria of the two querysets.

is there a way to find the GenericRelation fields on a model? they don't show up in _meta.virtual_fields

mattmcc: ah ok, I guess that's what I get for believing stack overflow, thanks!

Heh.

what's the best way to get a union?

Raw SQL. The ORM can't do them.

JDShu: Are you talking about a union in the SQL sense, or the mathematical set sense?

mathematical set

should I just do it in python?

you could call distinct()...

ah, if only we had a relational query language....

Then you want (qs1 | qs2).distinct()

(or is it +? I forget)

|

cool, thanks! let me try

sweet, this works, thanks again everybody :)

FunkyBob: is there more to this line? child = parent.childrel ...?

daveb: no... that's just trying to reference the child instance in case it already exists

you know... follow the 1to1 relation backwards...

got it

so the only way i've figured out to get GenericRelation fields from a model so far is to get all field names with _meta.get_all_field_names() then check each one to see if it's a GenericRelation. surely there must be a better way?

wilbur-d: why would you want to programatically find them?

wait... shit. actually i don't think i need to.

i THOUGHT i wanted to use them in a custom queryset. but i was thinking backwards

HAHAHA DISREGARD THAT, I SUCK COCKS

sorry, that was probably inappropriate. a little bash.org humor

it's been a long day

aw bash.org

fond memories

indeed, i sometimes forget how old i am

Silly question: One of the first settings in settings.py is BASE_DIR. Yet this is nowhere to be found in the docs. What exactly is the recommended place for BASE_DIR to point to?

in #python

red23: it's a helper for all your paths that need to be absolute

red23: it's not really a django setting

red23: and if you're starting a new project, you can probably leave it as what it defaults to

default: which is the directory that settings.py is in

no, the parent directory of that

if i try to run sqlclear output against my postgres db, it complaints about a constraint not existing. when i look at the db, it appears the hash at the end of the constraint name is 16 hex chars, but the sqlclear output has only 8 hex chars (different)

it defaults to your project workspace dir...

familiar issue?

this is with django 1.5.4 on ubuntu 13.10 fwiw

os.path.dirname(os.path.dirname(__file__)) I know this is python question but how is this the directory above settings.py

If the first dirname is the directory containing settings.py ..

ifdef42: did you change django versions at some point?

btw when i said "in #python" that was the last bit of "/join #python" that got misdirected to the wrong window, not a jab :)

FunkyBob: now that you mention it... :)

i was using django 1.4, and am trying to update to 1.5 on my way to pip installing the latest and fully migrating