waugust wrote:
Hey all,
I'm a RoR guy who came over to Django because I like Python more then
Ruby. That and Rails is like 70% DSL and Django is alot more Python
then DSL.
With that being said...
welcome
1) What's up with the lack of db schema migration!!?? That's really
half-assed. What's the point of an ORM if you have to write raw SQL to
update your models? So what's the solution here? I saw three out there
listed on the Django site, having the one most currently active being
South? thoughts?
South is definitely the best option IMHO. It does the job. Correctly.
Forget raw SQL and you can also rollback if needed.
2) No Gems. Why not have a central repository that tracks middleware
and its versioning?
Seems like a crap-shoot to use middleware if you don't know if its
being utilized, updated, or buggy.
I guess that looking at pypi.python.org should give you a hint.
3) This may be purely out of my ignorance: I don't care to have all my
models in my app in one file. Can't I just split them up in a
package? (put them in a subdirectory named models with a blank
__init__.py)
The only thing I saw on that would be to specify the app option in
Meta for each model.
with django, you can have your models in any files you want.
As long as I can tell models.py is only a naming convention.
you can have a class_a.py and a class_b.py which contain the
respective classes.
regards and welcome,
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to [email protected].
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.
