#django

hi all, i don't understand why my **project-level** initial_data.json fixtures (which just create a user) won't load anymore since django 1.7: Problem installing fixture '/home/jpic/env/src/session-security/test_project/fixtures/initial_data.json': Could not load auth.User(pk=1): no such table: auth_user. Any idea please ?

how can I write it then?

viwal_: I don’t understand your question

I just gave you a fully functional CreateView

yes

sure

tbaxter, In those cases, I just extend View, at least I dont have to keep checking request.method =='post'

at this case

but if I need any functionality that is not in any cbv?

bibhas: if you’re checking post, shouldn’t you at least be using FormView :-)

error (reproductible locally): https://travis-ci.org/yourlabs/django-session-s... and source code: https://github.com/yourlabs/django-session-secu...

how can I procced then?

viwal_: most pages are a list, a detail, or a form… things that generics handle. If you have a page that is not, then you get to decide what to do

tbaxter: and can I combine funct and cbv?

tbaxter, hehe. I just find it neat to write things inside a method called get() or post() :P

anyone familiar with the Meta class in forms?

viwal_, you can have one view as CBV, another view as FBV. You can't have a view using both or neither.

bibhas: hmm I understand ... anyway can see the reaso to use cbv ... I will complicate my work right now

jwhite007: yep, pretty much

jwhite007: you can do this kind of things: https://github.com/yourlabs/django-autocomplete...

and it's really really awesome what your ModelForm can do out of the box

is_null: http://pastebin.com/0A00VQth in my class Meta i render 'contacts'; however it's listing contacts for all of my users. how do i make the contacts user-specific?

oh, i thought you were talking about metaclasses, well there are many ways really, for a contact select i'd use an autocomplete field

is_null: each user will have multiple contacts.

…to choose from.

After restoring a database dump in mysql, I get "Field 'id' doesn't have a default value"" from User.objects.create_user

if your contact list is huge, a checkbox select or multiple select will be a bit unconvenient to use

is_null: can i handle that in the views function which renders the form?

Is there a good way to initialize those things when restoring?

jwhite007: you could, but it would be better to encapsulate that constraint in the form class, and maybe even enforce it at the pre_save level

is_null: i know how to build the form, but i want the form to only show contacts for a particular user, not all the contacts in the db.

is_null: does that make sense?

jwhite007: well you'll have to pass the user to the form or form field at some point

yeah it's pretty common

is_null: so… i'd pass the user to the form from the function in views.py… right?

that way works

then in the form you could use that user variable to update your form field's choices

is_null: how would i then use it in the class Meta?

wait, what are you trying to do with Meta ?

is_null: did you see my code?

is_null: http://pastebin.com/0A00VQth

jwhite007: yes ...

jwhite007: there is no magic option to filter a ChoiceField.choices queryset based on a value **which you are providing manually**, in Meta, nor anywhere else, to my knowledge

is_null: i'm just building a form from the model with class Meta.

is_null: hmmm.

is it terrible of me to use django.contrib.staticfiles.storage.staticfiles_storage in my code?

jwhite007: http://stackoverflow.com/questions/13539358/dja...

%s/choices/queryset/g

is_null: so…. i don't want a queryset.exclude, i want a queryset.include?

jwhite007: you just want to override the default queryset for the ModelMultipleChoiceField that your ModelForm generated for you

is_null: ok. that points me in the right direction. thanks for the link.

ie. self.fields['contacts'].queryset = self.fields['contacts'].queryset.exclude(not_visible_by=current_user)

or just make a new queryset, it doesn't make a difference

afaik

is_null: cool… i'll try and refactor my code. thanks for the tips.

doismellburning: sounds fine to me

SmileyChris: I'm never 100% clear on "API vs internal" in a lot of cases

hi all, i don't understand why my **project-level** initial_data.json fixtures (which just create a user) won't load anymore since django 1.7: Problem installing fixture '/home/jpic/env/src/session-security/test_project/fixtures/initial_data.json': Could not load auth.User(pk=1): no such table: auth_user. Any idea please ?

SmileyChris: (obviously some things are clearly API)

error (reproductible locally): https://travis-ci.org/yourlabs/django-session-s... and source code: https://github.com/yourlabs/django-session-secu...

doismellburning: technically any behaviour that is documented is safe

is_null: the auth_user table hasn't been created yet

is_null: is this a new DB?

you mean "safe" by "you'll be notified if it changes"

yep :)

safe, not sacred :P

extc: yes, it's the db created by ./manage.py test, but i can reproduce it with a new db as well

SmileyChris: https://github.com/django/django/blob/1.7.1/dja... doesn't look documented to me :P

SmileyChris: but good to know, thanks

is_null: is django.contrib.auth in your INSTALLED_APPS?

doismellburning: you should cover your code which relies on that by tests

is_null: good idea, I'll be sure to use version control too ;P

extc: of course, and note that this only happens with django 1.7: https://travis-ci.org/yourlabs/django-session-s...

doismellburning: nice one ;)

doismellburning: https://docs.djangoproject.com/en/1.7/ref/setti...

3rd para

SmileyChris: <3

extc: it's pretty weird, it "looks" like it's trying to load fixtures before it created any table at all

is_null: that would be silly :)

Creating test database for alias 'default'... Traceback: [here goes the traceback from loading initial_data]

it's here: https://travis-ci.org/yourlabs/django-session-s...

is_null: since initial_data is deprecated, it seems like a good time to change it to a data migration :P

SmileyChris: i'm sorry but i don't think it's possible in this case ;)

is_null: sure it is -- your data migration can load the fixture

can i make project-level data migrations ?

i thought migrations were for apps only

they live within an app, but you have dependancies on apps in this case anyway

like auth

surely you have a reasonably core app you can just throw the migration in

otherwise, make one that just does this

what ? really ?

what what?