Leor Barak Fishman

Wait, why nosql for this? this seems like a classic case for relationality, maybe postgres?

Sure -- so, mongo (and similar nosql solutions) are good when you have unstructured data, that you might need to modify within DB, and that doesn't need to scale to...

Ah, aight, then it's still best to have it as postgres/another sql install but it's less necessary. On Fri, Apr 3, 2020, 12:22 PM ainsleys wrote: > @FishmanL Just to...

I'm still getting this error on my end, on version 1.0.2

FWIW I had this problem internally, and handled it with a wrapper around privacy that did as follows: ```class PrivacyController(): def __init__(self, data_conn, metadata, max_epsilon, scaling_const=1e3): self.scaling_const = scaling_const init_privacy...

Also, RE serialization/rehydration, are a getter and setter for steps not enough?