#django

yutro

yutro dodo

dodo

I've handed in my resignation letter yesterday ... :)

oooh

next job firm in hand?

FunkyBob: not really, i would like to focus on opensource projects for a couple of months, and look for remote work ...

wait that sounds almost like me!

dodobrain: did you also quit your job? :)

jeh

and also same to your 'not really' answer to funkybob

hehehe, must be something in the air ...

of the rest, the 'remote' part is also true. only changes would be 'couple of months' and 'focus on opensource projects' :)

lets hope the dodos dont go extinct this time around ;)

O_o

dodos alike?

lawl, dodobas is like yoda compared to me when it comes to django

dodobrain: what ?

in terms of knowledge and experience i imagine

Which autocomplete package should I use? I'm typing in a TextInput and I have a queryset of objects to match it.

dodobrain: not sure about that, i've been mostly working in layers below Django

The options available will be different depending on the context

Morning. When using django test client with post, how do i add query params as well?

They'd go on the URL.

you have to urlencode them yourself :(

Bummer.

With .get() it's so handy that it does automatically with data.. wish there would have been similar thing for post/put/delete etc.

i don't think api is that obvious

but yes

Well, QueryDict for a rescue.

Next stupid question, how to test that .post actually redirected me to location x?

assertRedirects

hello, i am trying to make a .save() function on my model atomic, and I have a @transaction.atomic decorator on it. however, i am still getting concurrency issues. How can I fix these?

how can I start a database transaction to commit everything in one go?

transaction.atomic

what kind of issues?

fleetfox: same post id being saved multiple times

i need some kind of a lock on the database

weel that has nothing to do with atomicity

select_for_update()

shangxiao: ?

m712: ?

jarshwah: I'm trying to figure out how / where __exact is registered for a field. And following that, I want my subclass of CharField to only have two lookups __exact and __something where neither one is the default and each usage of that field *has* to specify one of the lookups explicitly

m712: https://stackoverflow.com/questions/129329/opti...

fleetfox: pessimistic locking is probably what i will go with

users would probably not want posts to be dropped

how can I achieve this?

😖

i want to lock writes on 2 tables, backend_board and backend_post, until I finish updating them

select_for_update()

okay

shangxiao: is that a queryset method?

thanks

that will prevetn concurrent updates, but assuming you have something like form posting scenario it doesn't work

two users open same form at different times

later they submit

last one will just overwrite

even though source for his post is stale

hmmmm

We were having a discussion about this the other day. There was a package that might be useful.

i think there are multiple packages

Yeah, likely.

is that what your issue is m712 ?

2 users open a post to edit at the same time?

The one I found that looked okay was https://github.com/gavinwahl/django-optimistic-..., but I think there was some stuff about it I'd do a different way.

shangxiao: i have a database id and a board_post_id

which is a board-specific ID

i have already done unique_together

Oh poop. My in-postgres idea using triggers to prevent bad writes dpaste expired.

lul

shangxiao: now, when I am creating a post, i check the total_posts number on the Board i am posting on, then set it to my ID, then increment total_posts by one.

you can see why it's having issues

probably select_for_update will fix this

schinckel: how you propagate to django from trigger? You will have to parse strings in exception, no ?

fleetfox: Yeah.

yeah, that sucks

yep so that doesn't sound like the problem that fleetfox described

shangxiao: does select_for_update wait until the end of an atomic block?

i mean

"described a solution for"

does it hold a lock

it does

pessimistic sounds fine for creation issues

okay, thanks a lot everyone

shangxiao: probably would not want posts randomly dropping ^^;

nah someone might get angry :)

i want you to understand that with naive locking you can still get phantom reads and other issues, depending on what you are doing it may be import

ant

from anthill import ant?

:d

fleetfox: curious as to what you meant by that

fleetfox: i just want to lock reads/writes on a table until i update it, which is backend_board

it's only gonna hold for a fraction of a second