> I have decided that I need considerably more control over both my HTML
and my database, which in point of fact is being moved from Postgresql
to MongoDB.
DB sure, but last time I checked django never took *any* control of my HTML (unless I specifically ask it to by rendering a form directly, and *even then* you can easily create your own form field widgets, or just render your forms manually)
> So, what are the dependencies for "forms" and "db". Obviously, I know
> that most of the "contrib" package is out. What else? Cause I'm
> thinking of maybe forking the Django project for my own use.
Wait, why are you talking about the dependencies for db *and forms*?
The ModelForms stuff depends on db as its purpose is to create forms *form models*, but forms themselves should be independent from models and useable regardless of your use of the Django ORM. And it's not like anybody forces you to use the built-in forms rendering.
> Cause I'm thinking of maybe forking the Django project for my own use.
Why would you *fork* django? Why not just stop using the ORM for your stuff (and stop using anything relying on the ORM obviously)? What would a fork bring you if your goal is just "I don't want to use the ORM"?
And if what you want is a nonrel datastore interface, why not use django-nonrel[0]?
[0] http://www.allbuttonspressed.com/projects/django-nonrel
--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment