#django

Hi everyone! I'm using django s3-direct to upload files from django to aws s3 service. Works great. Now I would like to be able to delete the file from django AND aws S3. Someone already tried that ?

I'm using an m2m intermediary model to state membership like information. companies can be member of multiple associations and associations can have many members. What does on_delete mean in "person = models.ForeignKey(Person, on_delete=models.CASCADE)" ?

Anyone knows if there is NaiveDateTime? I'm USE_TZ=True, but some of my fields are naive for legacy reasons

empedokles78: if person is removed it will delte your membership

fleetfox: I don't think there is, but you could subclass DateTimeField and change the to_python etc?

fleetfox, that might be unwanted (it could be transfered to another company), are there other options?

if i have two model managers on a model, how can i chain calls across the two managers, for instance Place.recommendations.for_user(user).live() where live is defined in the default "objects" manager

kezabelle: i think it's more involed

empedokles78: use PROTECT, and handle ProtectedError. Or if you can always resolve instance it should be transfered to use SET

fleetfox, That's over my head for now, so I should set it to "on_delete=models.PROTECT" currently?

Will "date_left = models.DateField(null=True)" do for a membership, which not yet has ended?

yes

guys i have a question

ok allow me to read your mind to find out what it is

you want to hire me and give me the big bucks?

lol

not really

I guess you'd better just type it out then

im using a dictionary that holds the format for a query that goes to elastic search. The problem is that in one of the nested dictionaries inside that dictionary i need to have duplicate keys - thats the way the elastic query works... how can i solve it?

I'm pretty sure elasticsearch doesn't require a dictionary with duplicate keys, since that's impossible. You're using the python lib I assume?

yes

does anyone here use multiple managers on a model?

fission6: probably

my bad - after your comment i double checked and you are right - it is a lost of dicts which both have the same key

arielfe1984: so you're using the querystring format?

fission6 - yeah

Knyght arielfe1984

if i have two model managers on a model, how can i chain calls across the two managers, for instance Place.recommendations.for_user(user).live() where live is defined in the default "objects" manager

yeah that's what I was about to get it

at*

Knyght - thanks a lot :)

fission6: don't think you can, you should instead use custom QuerySets rather than custom Managers

Knyght how would that work

would it be typical subclassing

like how would i be able to mix chained called

well your .live() is a QuerySet, right?

from an OOO subclass standpoint it would be a method on a QuerySet

or rather a qs method

yeah

sure

and it would return a an instance of QuerySet

hmm one moment I'm trying to use brain

you probably wouldn't attempt to chain calls between them, but to have them share a base class.

why not - what kezabelle said

thats kind of lame but seems like the only way

have a base manager that has live() and then your other manager uses it as a base class

sorry that has for_user

you know what I mean

so like have a base QuerySet class with "core" logic and then inherit that into other managers

for more buisness logic type "things"

technically there'd be managers, but I'd just do it with .as_manager() and have MyQuerySet subclasses.

ya

kezabelle Knyght do you two have. guiding philosophies on what should even be manager methods/queryset methods, ive heard people say you should not pass in parameters to them, and if you do to use more of a services layer that deals with parameters or with Two Models to get to some logic

I use custom QuerySets quite liberally

I try not to put too much in them other than db stuff, that's my main thing really, 'cause it feels like hiding code and sometimes it can be a bit unclear where it's coming from

I dunno, it's quite simple to me - if there's some query I need to do more than once, it goes in a custom queryset

do you have methods that do not return a queryset but perform some DB operations to get to a result

sure - delete() is builtin an example of that

I think those are terminal querysets, stuff like delete and aggregate

indeed. count, aggregate, update, delete etc.

hello there. using django 1.11. i've got a jinja2 template that has a comment string in it, like <!-- mycomment -->. I'd like to check for that string via a test: https://dpaste.de/yKsu

Knyght i find myself often doing this pattern, curious what your thoughts are I have a method on a customer Queryset Product.objects.for_company(company), then I have a model method on Company def get_products(self): return Product.objects.for_company(self) - so that i can do something like company.get_products() - how do you feel about this

however, the test fails. where am i going wrong?

s/mycomment/booklist template/

kezabelle feel free to weigh in too ^

Do I need to specify a field in the intermediary model which is set to null in the shell?

fission6: dunno - I probably wouldn't do it myself but I don't see much harm in it - maybe you miss out on some optimisation but haven't thought about it very hard

fission6: I've done similar, though I'd use the reverse relation rather than Product.objects ...

mostly because then I can (ab)use any prefetch cache that exists at the instance call time.

kezabelle i do the reverse relationship when it makes sense

avoiding littering .filter(...) or .all() (or {{ .all }}) around the place can be a valuable thing because then you can keep the existing API and wholly change the underlying code.

are HTML comments ignored by assertIn function calls?

plus you're making moves towards encapsulating data in one source of truth

kezabelle yea makes sense

just never knew if i was violating something through that pattern

finster: have you tried using assertContains instead

probably :p

but it comes in really handy, esp in templates

also the obvious things of showing us your template and making sure the comment actually ends up on the page at that url

Knyght: okay, thanks for the link. yes, i verified that the comment is visible when using a usual browser. in the test suite, however, it seems that the included template file cannot be found. still investigating