What about giving each Model a render() function to render it's
contents against it's template and return the resulting string. You
could then do something like this in the Display template:
{% for e in elements %}
{{ e.render }}
{% endfor %}
A more MVC-friendly approach may be to rende
Looks like my earlier reply got dropped. Sorry if this ends up being
a double post.
Check out the Model API docs:
http://www.djangoproject.com/documentation/db-api/#isnull
You want to do something like:
Year.objects.filter(event__isnull=False)
- Robin
On Apr 24, 11:15 am, "[EMAIL PROTECTED]"
Not a dumb question, but one that has been answered in the Django
docs. Have a look at http://www.djangoproject.com/documentation/db-api/#isnull
It sounds like you want:
Year.objects.filter(event__isnull=False)
- Robin
On Apr 24, 11:15 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I'll a
I think everything could be accomplished by creating a separate
settings.py file for each site, and pointing to them in your virtual
hosts. By installing your apps outside the project dirs, but still in
the PYTHON_PATH, you can refer to the same app dirs in all settings
files. The only problem I
On Apr 24, 10:58 am, Moses Ting <[EMAIL PROTECTED]> wrote:
> Hello DJ Users,
>
> I'm trying to write a generic template where I can auto-populate a
> html table depending on which model I use. So for example the view
> does something like this:
>
> def genericView(request, model):
> contex
On Apr 24, 9:14 am, "Craig Kuhns" <[EMAIL PROTECTED]> wrote:
> Does any one have any idea what that error is from. I am at work
> right now, but tonight I am going to dig in and see if I can find it,
> but if anyone has any ideas they would be much appreciated.
>
Craig,
It sounds like the bug
What about doing both? Write a pre_save record indicating the
operation about to be attempted. And a post_save indicating the
success of the operation, using a unique identifier to identify the
pair. Then if the post_save gets out of sync, you have a record of
transactions that may be at fault.
Craig,
Not sure what would be causing your error. But to answer your second
question, your files should automatically be uploaded by the
FileField. As long as the web server has write access, the files
should be uploaded to MEDIA_ROOT/upload_to where upload_to is the
argument to your file field
This is most likely because you're using 0.95 instead of 0.96. The
error is documented here:
http://code.djangoproject.com/wiki/IrcFAQ#WeirdError1
On Apr 22, 10:25 am, z0ltan <[EMAIL PROTECTED]> wrote:
> Hi folks,
> I have been bitten by the Python bug and have decided to jump
> into web de
Looks like the download link is broken.
On Apr 21, 4:24 am, Oliver Charles <[EMAIL PROTECTED]> wrote:
> Morning all
>
> I've been meaning to post this to the list for a while, and I think my
> code is now ready to be shown. I've been working on a small bug tracker
> type project for myself - as I
10 matches
Mail list logo
