Re: Catching Exceptions thrown in .save() / Best practice question

Malcolm, Spot on on all points. A ridiculous logic error in my model code was raising an exception in an unexpected place. A little bit of proper code review caught it. I appreciate your insights on this one. Cheers, Mark --~--~-~--~~~---~--~~ You received

Catching Exceptions thrown in .save() / Best practice question

According to a previous (http://groups.google.com/group/django-users/ browse_thread/thread/64a9558d5c02e39/c0c28daed410898d?lnk=gst=catch +save+exception#c0c28daed410898d) post it's bad practice to wrap a model's .save() in a try/except. Adrian suggests using manipulators instead. I'm writing a

Re: Development / Production Setup

Thank you both SmileyChris & Nimrod putting what you've both suggested solved the issues! I really appreciate the help. Cheers, Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To

Development / Production Setup

I've been hacking around and googling for a little while now and can't seem to track down a solution to what should be a pretty straight forward problem. The situation I'm trying to setup a nice workflow between my development environment and my production environment. I would like

Re: Relationships in Models across apps in the same project

Branton, Just to re-iterate I did say I was a Django noob! You answer worked like a charm. I really appreciate it! I'll check out the django-tagging app shortly. Cheers, Mark PS > I'll have to submit an update request to the documentation to clarify the wording.

Relationships in Models across apps in the same project

I'll start off my fully admitting that I'm a Django noob and there's probably (hopefully!) an easy answer to this one. Problem: I have several apps in the same project. Each of these apps offers tagging of various models. Ideally I would like one Tag model in an app (e.g., a tagging app) that