PJ Farrell
PJ Farrell
Yes, PR are welcome. On Tue, Aug 4, 2020, 12:29 PM Abder wrote: > Hi, is this still open? > > — > You are receiving this because you commented....
PR welcome if you can figure out how to parameterize it or another solution could be to use Postgres dollar quoting.
@User3759685 Not sure this can actually be implemented. Due to the encryption, all Django-PGCrypto-Fields are stored in the DB as `text` fields (unlimited character length) including Date, DateTime, etc. The...
@steezeburger there's no functionality in this library to do this as the library is specifically to make field level db encryption transparent to your Django application. Django has a meta...
@SiddharthPant It's currently not configurable in this package but a PR would be welcome.
This is also related to #89
Just wanted to ping @ezheidtmann about the status of getting some tests in the PR before merging code. Do you have an ETA?
@ezheidtmann - Just to confirm -- the load data issues you describe only occur on M2M in which the model has changed? I don't understand the issue enough just based...
See PR #343 to fix the parity issue between the list and detail views.
We are using the code in the PR and it works as expected. +1 on getting this merged in ASAP.