#django

Is Model.clean and Model.full_clean called on save?

In fact, why isn't Model.clean called on save?

Is this a bad idea? https://gist.githubusercontent.com/glarrain/544...

hi there, sorry to ask this here, but #restframework looks pretty dead right now - in django-rest-framework is there any option for having somewhat polymorphic serializer ? I mean sometimes i want to serialize more fields than i want to deserialize, and it is pain to deal with additional fields in serializer and stuff. Is there any pattern for that ? Maybe i should just have more than one serializer per model ? although that doesn't

seem like very good, DRY approach

hm. how about inheritance?

class BasicSerializer, class FancySerializer(BasicSerializer)

dang`r`us: that is actually something i didn't think of....

arlekin: so you want to read only a few feilds but display more?

pyjacker: i have serializer for model, and i would like to use it for both when i pass whole object from form, and when i only retrieve say pk and name for displaying in select field for instance

You can also set fields to read_only, not sure if that's exactly what you're looking for

write_only and hidden are kwargs for serializer fields in django rest framework.

arlekin: write only seems like what you're after..

pyjacker: do i understand correctly that field set to write_only would be applied only when deserializing incoming stuff ?

As in it being only writable, yes.

whats the easiest way to create an initial data fixture?

great, that - and the inheritance approach - should cover all my needs

thank you very much dang`r`us, pyjacker, TheJoey

surfnturf: use the admin, then dumpdata.

pyjacker: thx

I want to have the same form for editing and creating objects. Should I use a single django.forms.Form for those?

Some button names will be different between the 2 cases, and "edit" form will have the values prepopulated

Can I use the same django form for those 2 cases?

the submit buttons aren't part of the Form anyway

I thought the tutorial covered using the same form for create/edit

I'm quite sure the docs do

Oh, really? could find it

couldn't*

the tutorial doesn't use django.forms

FunkyBob: iirc the django tutorial covers creating an html form for submitting votes, but never touches django forms or modelforms

amikrop: Check out https://docs.djangoproject.com/en/1.8/topics/fo...

thanks

okay now I need to figure out how Django does GROUP BY...

looks like aggregation is the deal.

Volund: This might be helpful http://www.laurencegellert.com/2015/06/example-...

aggregate and annotate

soo... this, maybe.

participants = self.poses.exclude(ignore=True).values('owner').annotate(total=models.Count('owner'))

basically looking for SELECT owner,count(poses) from poses where ignore=False GROUP BY owner

err

count of something

Why is model level validation discouraged?

actually

whee... another nap release, now with even more docs!

cool, FunkyBob

MarkusH: if you're alive... I've made datamapper fields a little less tedious :)

so i'm assuming there's no way to dynamically add fiends to a model since _meta.fields is an ImmutableList (django class)...wondering if anyone has messed arouond with that idea

cereal: are you also dynamically fucking with your DB schema?

naw

just adding fields dynamically

so...

but not effing with the db

why?

because i need to

...

don't be a twat... explain the problem so we can help you

right now i'm just adding them as variables to the class

I've tossed the idea around a few times

but essentially i'm working on allowing dynaimc fields for differnet models of my app

aka, tennant a wants to track some random data but tennant b has zero need for that particular data

and so forth

sounds like what django-hstore's "schema" option can do

adds virtual fields

What is the default max_length of models.CharField?

i.e. what does None indicate

yeah, I messed with hstore but filtering isn't there for anything other than exact string matches

there isn't one

i mean, it works don't get me wrong

amikrop: IIRc you must specify a length

cereal: well, where are these values to be saved if you're not modifying the schema?

FunkyBob: https://docs.djangoproject.com/en/1.8/ref/model... seems to say max_length=None

amikrop: yes, and it has a check on it that says you must define one

but hey, you can keep arguing with me if you like...

FunkyBob, i'd catch them during a save and handle them that way

ok, but why would I argue?

just asked

right now i'm doing custom forms for this and its working

just exploring if there's a better way

amigo: as I said... you MUST specify a value

i got distracted by looking at a fields concrete method, and so forth

but that might not be the best option

cereal dynamic fields sounds very problematic, maybe what you want is a "key-value" model that links to the original model if hstore doesn't solve your use case?

i'm currently just having different models for each data-type right now

i'm just trying to make it a little cleaner when using it

Anyone more experienced than me care for a SO question?

its working pretty well, and yea its certainly going to be a bit more intensive than your normal model but sometimes thats just a need

pyjacker: did you try asking in #restframework ?

Yes.

I think the question has relevance for both channels.

I find the question interesting, because I recently added automatic calling of model-validatin into nap