So. If you aren't using a relational db, maybe you don't really want to be using subclasses of django models to pull your data out of SVN. My initial thought would be that you should do something like write an abstract class that has the necessary methods for providing the CRUD equivalent actions + any SVN specific ones (Revert) in SVN, and then subclass that in your models.py as you define specific models. This way you've at least created a bunch of objects that are hopefully mostly using the same code to access your repo. I'm no expert though and would love to hear what others think about this.
On Mar 27, 7:09 am, "Rishabh Manocha" <[EMAIL PROTECTED]> wrote: > Hey guys, > > I'm starting work on a project and for now, won't be using a db with > it. Instead, I'll be using a library which fetches all the data I need > from a local SVN store. I was wondering where should I access this > library from - the model (models.py) or the view (views.py)?? I don't > know if there are any restrictions built in for this case, but in > either case, I want to be doing things as are expected to be done in > Django. I'm inclined to just put all the code in views.py itself, but > I figured I'd ask what the community felt. > > Thanks, > > Rishabh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
