Hi, I've been tasked with making a django app that will need to support versioning of some documents.
I've been looking at your code to familiarize my self how to approach versioning.
I see you keep two models, one for current version and the other for past revisions? That's what I was thinking too ...
What I need to know though... you use content type to make a connection to the model which you are versioning, which is great I guess, so this app supports versioning of *any* model basically, but I will know which models I want to version (only one, maybe two), so I would remove this extra step, to simplify the queries a bit if nothing else ...
How heavily would this break your app? I guess just removing the field from the model will not break it too much but I don't know exactly where do you use this field ... so do you think it's too much work to remake your app to work like this and secondly, would you even recommend doing this or is it unnecessary.
What I am making will be an enterprise app for a fairly large firm with about 1000 concurrent users using it, so it needs to be scalable at least a bit. and secondly do you think there are any other potential bottlenecks with using your app?
Looking forward to hear your thoughts
or anyone else if they got an opinion ...