|
fabric!
|
# ¿ Dec 17, 2010 22:19 |
|
|
# ¿ May 15, 2024 04:42 |
|
Yay posted:We're ghetto fabulous, and use bash/svn export/rsync. I tried showing my boss Fabric, and he didn't seem interested ("What does it get us that bash doesn't?" - I've not used Fabric, so couldn't easily answer). It gets you the mantras of deployment: Repeatability Maintainability and Anyone on the planet would actually want to work with this-ability
|
# ¿ Dec 19, 2010 20:43 |
|
code:
|
# ¿ Jan 5, 2011 11:55 |
|
Take a look at how FilePathField is implemented (http://code.djangoproject.com/browser/django/trunk/django/db/models/fields/__init__.py#L817), now copy that for your logic.
|
# ¿ Jan 10, 2011 20:27 |
|
Those 2 are equivilant in every way. You can't select_related a many to many (or any multivalued relationship).
|
# ¿ Jan 21, 2011 04:15 |
|
Hanpan posted:Ahh yes, I forgot about all that crazy salting. If you put a GenericRelation on the Entry object then it will get deleted automatically: http://docs.djangoproject.com/en/dev/ref/contrib/contenttypes/#reverse-generic-relations
|
# ¿ Feb 3, 2011 21:49 |
|
If you think there's a problem with the docs, please please please file bugs on them, including just needing more details.
|
# ¿ Feb 14, 2011 17:02 |
|
Captain Capacitor posted:Never worked for Twisted Yes it is. We take our documentation seriously.
|
# ¿ Feb 15, 2011 03:02 |
|
That stuff isn't called by clean, it's called by full_clean (or maybe _full_clean).
|
# ¿ Feb 27, 2011 01:57 |
|
Wouldn't touch it. Just use mod_wsgi or gunicorn behind nginx and be happy. ps: 1.3 is out
|
# ¿ Mar 23, 2011 17:12 |
|
Putting MySQL in the working category, that's cute. Just try: referential integrity at the same time as full text search, actually useful GIS queries, deferred constraints, optimizing queries using IN, the list goes on... The error you're seeing is because you got an error in your transaction and ignored it, once a transaction enters an error state it must be rolled back.
|
# ¿ Mar 29, 2011 12:54 |
|
Yay posted:Additional note: calling form.save() should do the work of Order.objects.create for you. (Aside: what's wrong with creating instances of Order()? I've never encountered anything that said that was bad, nor have I had any problems with it) You probably need `order.save_m2m()` as well.
|
# ¿ Apr 1, 2011 00:31 |
|
|
# ¿ May 15, 2024 04:42 |
|
Lamacq posted:`form.save_m2m()` I think you mean. `save_m2m` is defined on the ModelForm, not the Order instance IIRC. , I think I'm going to go commit something to forms to drown my sorrows.
|
# ¿ Apr 1, 2011 18:17 |