Hello,
I'm going to introduce a new Django-based open source project.
It is a web application that interfaces cloud-computing infrastructure
as course labs which can be used by students and professors in
universities. We are in still in very basic level, but with many
people's contribution, I'm
See a recent thread here:
http://groups.google.com/group/django-users/browse_thread/thread/0ee03167b7b5e873/850ac8304bf952b4#850ac8304bf952b4
and this query:
mymodel.objects.extra(select={'ordering_field': 'IF(STRCMP
(bbs_tag.name, 'notice'), '',bbs_tag.name)'},
order_by=['ordering_field'])
Thanks, that works! (but I already changed my implementation not to
use tag-based ordering...)
For more generality, you could replace bbs_tag with Tag._meta.db_table
value.
On 8월4일, 오후11시25분, krylatij wrote:
> Use extra() method of query set with little hack ;)
>
>
I've tried that also, but it ALSO only accepts field names. Its
intention to be there is not to override previously set order clauses.
On 8월4일, 오후5시56분, Daniel Roseman <dan...@roseman.org.uk> wrote:
> On Aug 4, 8:28 am, Daybreaker <daybreake...@gmail.com> wrote:
>
> > I
not so much clean...
On 8월4일, 오후4시28분, Daybreaker <daybreake...@gmail.com> wrote:
> I want to run a query like this:
>
> select * from bbs_article a, bbs_article_tags a2, bbs_tag t where t.id
> = a2.tag_id and a.id = a2.article_id order by (case when t.name =
> 'notice' th
I think you have to remove the opening/closing brackets inside your
regex pattern.
Your regex currently means "one character that is a digit or a plus
sign".
Cheers,
Joongi Kim
On 8월4일, 오후4시09분, gentlestone wrote:
> I've got this error message:
> ---
>
I want to run a query like this:
select * from bbs_article a, bbs_article_tags a2, bbs_tag t where t.id
= a2.tag_id and a.id = a2.article_id order by (case when t.name =
'notice' then '' else t.name end)
which has a custom ordering rule.
As far as I know, Django model currently does not
Thanks, I just reported and found that ticket with your little
help. :)
It seems this problem doesn't have trivial solutions -- I think it
should be documented clearly, or fixed (improved?) later.
On 8월4일, 오전11시59분, Russell Keith-Magee <freakboy3...@gmail.com> wrote:
> 2009/8/4 D
I've fixed the wrong url templatetag to this:
{% url lab:bbs:view
url_key=lab_object.url_key,board_id=board.id,article_id=item.id %}
...but still I'm getting the error.
On 8월4일, 오전11시37분, Daybreaker <daybreake...@gmail.com> wrote:
> I've slightly fixed the pasted code for readabilit
I've slightly fixed the pasted code for readability, and so the url
templatetag example should be:
{% url lab:bbs:view url_key article_id board_id %}
On 8월4일, 오전11시34분, Daybreaker <daybreake...@gmail.com> wrote:
> Hello,
> I just started to use URL namespace that was added in the
Hello,
I just started to use URL namespace that was added in the 1.1 release.
I have a somewhat complex url configurations like this:
http://dpaste.com/74963/
And in a template, the following url templatetag is used:
{% url myapp1:myapp2:view url_key id1 id2 %}
I'm getting an error
a customized admin view for User model,
but if I try to admin.site.register(), it says 'already registered'.
On 7월29일, 오전10시27분, Karen Tracey <kmtra...@gmail.com> wrote:
> 2009/7/28 Daybreaker <daybreake...@gmail.com>
>
>
>
> > I meant, the phenomenon that mod_wsgi b
I meant, the phenomenon that mod_wsgi behaves differently with my old
conventions.
Sorry for my short English.;;
On 7월29일, 오전3시42분, Karen Tracey <kmtra...@gmail.com> wrote:
> 2009/7/28 Daybreaker <daybreake...@gmail.com>
>
>
>
> > I've solved this problem.
&
imported
them from models.py), but for whatever reason, this does not work with
Django 1.1 + mod_wsgi.
I'm not sure this should be considered as a bug or not.
On 7월28일, 오전12시39분, Ramiro Morales <cra...@gmail.com> wrote:
> On Mon, Jul 27, 2009 at 12:20 PM, Daybreaker<daybreake...@gmai
12:20 PM, Daybreaker<daybreake...@gmail.com> wrote:
>
> > Seehttp://code.djangoproject.com/ticket/11563:)
>
> > Yes, I had to ask it here first, but I didn't think autodiscover() is
> > the only(?) way to be recommended, so I thought that was a bug.
&
See http://code.djangoproject.com/ticket/11563 :)
Yes, I had to ask it here first, but I didn't think autodiscover() is
the only(?) way to be recommended, so I thought that was a bug.
So my question is the last comment there -- Is autodiscover() the
only way that is recommended as the official
I'm developing & administrating a django-powered website.
It's still in beta phase, so some errors are found by users.
I want to make an automatic error reporting system. How can I handle
500 internal server error or exceptions 'somewhere' in my code?
I've made a standalone program that uses Django modules.
At settings.py:
import os
PROJECT_PATH = os.path.dirname(os.path.abspath(__file__))
At standalone script:
import sys, os
try:
import settings # this file was in the same directory of
settings.py
Hello, I'm new to Django development. Here is my first question. :)
I have a model which has a 'file' FileField.
class Jewel(models.Model):
...
file = models.FileField(upload_to='attach/vault/file/')
...
I wonder how to access upload_to property in views. After reading
Django
19 matches
Mail list logo