For pages under admin control, yes, we need a full system history. For
other tables what we need is more narrowly defined. I have very clear specs
on what I need to log. ATM performance is not a concern.
On Fri, Dec 15, 2023 at 8:37 PM Mike Dewhirst wrote:
> You seem to be asking for a full hist
No, I have not see django-simple-history - thanks for the pointer - will
check it out.
On Fri, Dec 15, 2023 at 9:02 PM Mike Dewhirst wrote:
> Just thinking about it again ... you could look at the Admin source to see
> how it is working now and perhaps find a way to include the missing info in
>
django-simple-history is close to what we need. The one issue I see
(so far) is that it does not support tables that are created behind
the scenes by django to handle one to many relations that do not have
models. Does anyone know how to maintain history on those?
On Mon, Dec 18, 2023 at 2:48 PM L
Why you have heroku in your log? Remove all old dependency configs in your
settings first and then you need specify
```python
STATICFILES_DIRS = [
os.path.join(BASE_DIR, 'static'),
]
STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles')
STATIC_URL = '/static/'
HOME_DIRECTORY_SELF_STORAGE = o
Those many-to-many relations most certainly can have models and all of mine
always do. It is more explicit to do so but more importantly they generally
carry essential real-world information about the relationship itself.I haven't
looked at django-simple history beyond deciding to roll my own bu
On 19/12/2023 9:51 am, Larry Martell wrote:
Hmmm, in my case I do not see any models for those in any of my
models.py files. Where would I expect to find them?
You have to write them yourself. The best way is to run manage.py
inspectdb > models.txt then extract the m2m models from there. In th
6 matches
Mail list logo
