#django

"adding" and "db"

I see, that makes sense. I will use my own then, guess a signal wont work for sending these messages to my messaging queue

...and it's undocumented, so don't rely on it

iirc a Form can tell you which fields it updated

I wanted to know like who requested the change, the changed from to type stuff

you won't get who in a post-save signal

Yeah, that is why I was thinking if I could send my own kwargs down that would be nice

you can, technically

because the ORM can't even assume there is a "who"

^

you can keep around an execution context singleton of some sort, and set it in the middleware

yes, you can hack it in... but... blech

Right now I am just doing it in the view, but that doesn't really cover the admin

who cares about admin?

Well, I've done soemthing dumb and only allowed some action that are really super to happen in the admin but I need those to also send the messages (an after thought)

Like create staff users (admin only, but I need to send the user create command to our other servers)

Electrometro: you really shouldn't be using the DB Admin interface for your management interface

I completely agree. I just wanted some very infrequent super admin stuff to happen there.

I will refactor to have the APIs use it. Moving the message sending to the save/delete of the model. Going to pass in kwargs from the serializer context. Should work ok

I'm getting this ' Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.' repeatedly after resetting the database too. How to get rid of it ? I'm using Django app.

I tried migrate and makemigrations, no luck.

I'm on heroku.

Hi all, if I have custom validations for a model which can only be edited from /admin should I put the validations on the model or in the admin?

souravbadami: are your migrations committed and pushed?

Koterpillar: Yep!

bmon: There's no built-in hook for admin-specific validation. Put it on the model, and it'll be run by the regular ModelForm validation process.

souravbadami: then you should be getting the same on localhost; are you?

Okay, I have a situation. Earlier it worked using this. I use mysql locally and postgresql on heroku. So does that matter ?

souravbadami: try postgres locally?

Hmm, On it.

also, which migrations does it create on heroku?

some changes on a mode.

*model.

mattmcc: Thanks :)

souravbadami: post those, please

Migrations for 'app':

app/migrations/0002_auto_20161129_0304.py:

- Delete model mynewusers

- Add field owner to newreport

are you sure heroku app is up to date?

ensure it is

if it's still the same, post the models and migrations for this app

Yes, It is. Just pushed to confirm.

There's a single model with 4 charfields.

can you run 'git status' on heroku?

and git log

you can do: heroku run ls to see what's there

the point is to compare your models to the models on Heroku

souravbadami, Koterpillar you should definitely be running makemigrations locally, committing and pushing the migrations, and just run migrate on heroku

and also, unless you want to answer 10 more questions about models, just post them in full

I'm running it like

heroku run python manage.py migrate

that seems correct

and what output do you get back?

it completes successfuly?

I believe that spins another (temporary?) dyno that is destroyed afterwards

so you lose all the changes from makemigrations

I'm getting this ' Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.' repeatedly after resetting the database too. How to get rid of it ? I'm using Django app.

I tried migrate and makemigrations, no luck.

I'm on heroku.

souravbadami: if you are using postgresql, you can run: heroku pg:psql

that lets you poke around the db

if you're using sqlite, that isn't going to work on heroku

(filesystem is ephemeral)

souravbadami: paste the full output of what your models look like, and what do they look like on heroku (heroku run cat app/models.py)

Koterpillar: if you're using the filesystem for db on heroku, that definitely worn't work,and if you are using a db addon, that's independent of the dynos

I'm using db addon.

jessamynsmith: that's what I suspected, so their new migration gets lost immediately (which is rather good, actually)

souravbadami: postgres?

yes

ok, cool, then you can easily check if the migrations are logged in the db: heroku pg:psql

jessamynsmith: they aren't even created

jessamynsmith: and if they manage to create any, it'll be a headache because they are not in Git

Koterpillar: souravbadami is trying to makemigrations on heroku? that will most definitely not work

yeah, exactly, migrations need to be in git

(14:16:33) souravbadami: heroku run python manage.py migrate

It worked earlier, As I said.

Koterpillar: that's running migrations on heroku, which is correct, assuming they've already been created with makemigrations and committed

souravbadami: post what I asked for

jessamynsmith: right; I'm guessing makemigrations is also run on Heroku; no direct evidence in chat but let's see the models

Is there something misleading in the docs that suggests you should create migrations anew on production, because it's something we see quite frequently.

schinckel: depends on your dev process

schinckel: I think there should be an explicit point saying "don't lose migrations"

schinckel: and then "commit migrations"

several times

Yeah.

schinckel: if you don't need migrations go ahead and delete them

souravbadami: that's from where?

I can't see a workflow that makes sense to delete migrations.