#django

I have USE_TZ=True everywhere

I think, approximately, you never want USE_TZ=False

MarkusH: I just did and it seems to work

lxer: until it doesn't :-P

doismellburning: +1

using USE_TZ=True is creating other problems for me. like the format of datetime.datetime.now() is different, so I cant just do a compare with the timestamps I have in the DB

..."format"?

it looks different :)

and that stops you comparing how?

lxer: you want to use django.utils.timezone.now() anyways

"do a compare"?

gp

hey I just started using django about a week ago. how would I know :P

lxer: Didn't you read through the entire code base as everybody else? *justkidding*

lxer: https://docs.djangoproject.com/en/1.7/topics/i1...

So many control files in django to keep track of, pls suggest some graphical tools to manage them

Mississauga: what are control files '

?

manage.py urls.py settings.py etc.

hey, i was about to write a test that checks whether a migration should be added. first question, how can i do that? second question, is there a reason why "makemigrations --dry-run --noinput" asks for input?

i would have done that but i don't know how i can handle the input with call_command.

jaykay: the latter is a bug

Mississauga: you never alter manage.py ... settings.py is the root of your project... urls.py is whatever and wherever you want it to be [since you specify it in settings.py]

MarkusH: a known one or should i report it?

Mississauga: in fact, manage.py is just a convenience wrapper for django-admin.py

jaykay: looking for the ticket

jaykay: https://code.djangoproject.com/ticket/23407

Mississauga: so... what trouble are you having in "managing" these files?

MarkusH: thanks.

So now I have USE_TZ=True and TIME_ZONE='Europe/Berlin', but my time timestamps are still UTC . ( my timestamp is added automatically set in the model models.DateTimeField(auto_now_add=True, auto_now=False) )

lxer: yes

lxer: s/but/and/

so, can anyone tell me how i can test whether there are model changes that don't have a migration yet?

thats fucked up :P

jaykay: have a look at the runserver component

lxer: why?

that does a check for missing migrations

Mississauga: a better question, I guess, is what are you using as a basis for comparison?

MarkusH: if you are referring to the "there are unapplied migrations" message, that's not what i want. the problem is not unapplied migrations, but migrations that don't exist yet

jaykay: ah, ok

doismellburning: because now if I want to check when something was created (and if it is older then now(), in my case ) I always have to add +1 hour..

jaykay: https://github.com/django/django/blob/master/dj...

lxer: ...why?

lxer: demonstrate this in a gist please?

jaykay: or on 1.7: https://github.com/django/django/blob/stable/1....

lxer: (this sounds like you misunderstand timezones)

in django-rest-framework, if i am using token-auth, will request.user automatically be the user who has authenticated via the token?

MarkusH: well, yes... that's a lot of code i'd have to copy to get to that line... :) it's quite unhandy that this is one large block of code

is there a way to connect django 1.7 to mongodb?

i could only find django-norel for 1.5

gener1c: sure... pick whatever python mongodb driver you want, and use it

gener1c: in what way do you want to "connect" django to it?

gener1c: ^ re "in what way"

(mongoengine was good last I looked)

gener1c: do you want to plaster layers of crap on top of it to make it look like a relational store, so you can access it via the ORM?

or do you want ways to make forms work nicely with mongo documents?

is there a more elegant way to roll back a migration?

i just made a migration, but i'd like to go back to the way it was before

should i just migrate again?

limbera: you can do "migrate <migrationname>" to migrate back to some other migration. or did i get the question wrong?

FunkyBob: why not both?

thanks

limbera: if you haven't applied the migration _AND_ it is the last one in that app: remove the .py file

gener1c: because trying to make a dog quack is silly

gener1c: why would you use mongo if you actually want a relational store?

so I'd actually prefer a quacking dock :þ

Hi all. Django and IRC newbie here…

that is true, it looks like mongo's native language is a lot more like orm already

(over a barking one that is ;))

Got a question if I may…

gener1c: it's nothing to do with the query language

roger-gordon-old: just ask :)

it's the fact the ORM is an Objed -> Relational Mapper... and Mongo is quite specifically a non-relational store

i dont want a relational store i just want to use django without needing to care what database is behind the orm abstraction

gener1c: well, you already have that

I have a project that I created a while back using django 1.5. I want to upgrade to 1.7 now. What should I do?

Django can already more or less transparently use several DBMS out of the box

and there are a number of high quality 3rd party libs to support more

roger-gordon-old: go through the release notes and change what's necessary.

gener1c: Sounds more like you want to require precisely one database (mongo)..

OK, that sounds straightforward. Thanks!

roger-gordon-old: what i did is: got test coverage up to 90% and run that with "python -Wall". it will tell you most of the features that you use and that are deprecated. maybe first upgrade to 1.6, then repeat that process before upgrading to 1.7.

Thanks MarkusH.

roger-gordon-old: I'd recommend going via 1.6

I’d also like to upgrade Python to 3.4 is this recommended?

roger-gordon-old: can't see many reasons not to

FunkyBob: so ill have to disable the authentication, admin and sessions components if i want to use mongo and there is no going around it?

Thanks FunkyBob, doismellburning and jaykay.

gener1c: something like that... at least the Django supplied ones - except sessions, it has pluggable storage backends

gener1c: must admit I'm curious what it is you're doing that will benefit from using an unreliable document store like mongo...

gener1c: "i just want to use django without needing to care what database is behind the orm abstraction" - if "database" -> "relational database" then this holds

i am using the database as a backend for celery to do a lot of intensive tasks, the configuration of the tasks is done from a web interface and i wanted it to reside on the same db

...and?

got a better idea

?

use postgres

(oh and don't use it as a celery broker)

so i need 2 seperate databases, there is no escaping it

different*

gener1c: no, you need a database and a queue

(fsvo "need" ("want with a high probability"), "database" ("relational database"))

One of these days when I have free time, I'll check out PGQ.

i use rabbitmg as the broker

fair enough

but i need some sort of persistency in the backend so i chose mongo

gener1c: if you're using rabbitmq, what's the bullshit about using mongo?

mattmcc: you mean in your next life?

oh, mongo is relibly persistent now?

hehehe

MarkusH: Something like that, yeah. :P

gener1c: why pick mongo, again?

gener1c: or, pick postgres, and have an easier life

cause it's the new (old) cool (but not so cool) shit out there

and marketing!

for a bit there, it seemed you were saying you were using it for the job queue...

apollo13: marketing which tended to be "it's just as trustable as mysql, but not as slow!" ... wasn't it?