#django

always

but I'm sure you're asking about specific issues?

and i try to use Value(now(), output_field=DateTimeField()) in a query, but it produces a syntactically incorrect postgresql query

erm

notably the query has '<a date string>'::timestamptz

you want to pass now() into the query?

yeah

why?

i was making something that was a bit db-agnostic

why not ask the DB for now?

and i found that passing in now() worked nicely

CURRENT_TIMESTAMP is quite DB agnostic

how do i do that?

I opened a ticket recently for adding that... and jarsh suppklied the code

FunkyBob: https://dpaste.de/w90o doesn't make sense

JohnnyZ_1: when moving from 1.6 to 1.8... did you '--fake' apply any migrations?

FunkyBob: I faked the initial

just the initial? iirc contenttypes has 2 migrations

how do i put current_timestamp in the query?

as i understand F expressions only work for the fields in the view

should i make a Func class to do it for me?

rray: well, I was suggesting you look up the ticket I mentioned, since it has the code

oh ok cool

ty

this channel has been very helpful thanks guys

learning through teaching

FunkyBob: yea only the initial which has the include contenttypes as a dependency. I didn't see it in my next migration. What should my next steps be?

Another thing: when I remove 'django.contrib.sites', and 'registration" out of my settings. contenttypes migrates successfully. no migrations to apply.

sorry, what? I meant did you fake any migrations on any of the other apps, like contenttpyes?

No, I do not believe so

the most likely reason I can think of for the error you're seeing is that contetypes wasn't migrated properly

if you "showmigrations contenttypes" what does it show?

[X] 0001_initial

[X] 0002_remove_content_type_name

can you check the actual DB table? see if it realyl has removed 'name' from that talbe?

Hm. surprisingly it didn't

so, fake migrate contenttpyes to 0001.. then real migrate it to 0002

ok done

name still exists

even after Applying contenttypes.0002_remove_content_type_name... OK

exactly what did you type?

./manage.py migrate contenttypes 0001 --fake

./manage.py migrate contenttypes 0002

which dbms?

mysql

bizarre

Should I forcefully drop a column? Kind of annoying

Doesn't make much sense

well, you shouldn't need to... the migrations should take care of it

actually

wait it did

but hey, it's mysql.. so...

I apolgize

ah, ok

I had to refresh it

dumb.

ok so thats done now

let me try to migrate with the registrtion

Hey Bob, not sure the best approach to go about this. So I did a manage.py migrate. Said (1050, "Table 'portal_user' already exists") so I went ahead and did manage.py migrate portal 0001 —fake - that went through then migrated to the next migration and it took. Now getting (1050, "Table 'django_admin_log' already exists")

nvm

fake migrated admin

FunkyBob: thanks for your all of your help. enjoy the rest of your weekend!

JohnnyZ_1: python manage.py migrate --fake-initial (if you're on 1.8)

Yea took care of it. thanks:)

Cannot figure out why this is failing, and it is only sometimes. Traceback: https://dpaste.de/OTfv

Recently downgraded from django 1.8 to 1.7

why downgrade?

Wanted to use a module that doesn't support 1.8 yet

django-fixtureless if you are curious

make sure you've removed all the old .pyc files

what does that do?

its for fixtureless testing, generates test data automatically ;)

like factory-boy or model-mommy ?

I guess so, couldn't remember the names of the other ones so I tried this one

Alright, just deleted the .pyc's

Testing now

Im afraid it is the same thing

when you "downgraded'... did you pip uninstall django ; pip install django<1.8 ?

or did you just pip install django<1.8 ?

changed my requirements.txt, then did --force-reinstall

pip uninstall django

mk, testing again

same

exactly the same?

yup

and this worked in 1.8?

ah, no, it won't

because ExpressionNode doesn't exist in 1.8 I think

Yes, it worked perfect with no intermittent errors.

the reasl question is why is your django trying to import it

Im not in any of my code.

I am using celery

wonder if it is int here

well, what's odd is it appears to be django trying to import it

which is why I thought you might have mixed code from the upate/

it is in 1.7

1.8 does not

so what do you have in your requirements to install 1.7.x?

Django<1.8

1.7.8 is installed

not sure if that is a beta or something

no, it 's not

And the weird thing is sometimes the task works just fine.

How can I help you help me? Not sure what information would be useful for tracking this down

might just switch back to 1.8

Can't call time.sleep() in django test? Got an async call that updates a profile, want to check the status after the update is for sure complete

Scratch that