hi,
the documentation for use_for_related_fields states that it shouldn't
be used for filtering results:
http://docs.djangoproject.com/en/dev/topics/db/managers/#do-not-filter-away-any-results-in-this-type-of-manager-subclass
i just wanted to know if this advice should always be followed (or
when
hi,
i have tried to fill out the table for my project (sphene community
tools). but.. umm..
"500 Internal Server Error (Submission rejected as potential spam)"
to sum it up:
On Feb 25, 7:15 pm, akaihola <[EMAIL PROTECTED]> wrote:
> - posting without registration
yes, can be configured (if captu
On Jan 4, 9:28 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> newforms, etc.). I choose to use Hibernate and Freemarker for the
> Model and Template but these could be easily switched out.
since you are working with hibernate you might also be interested in
my project where i tried to port
Hi,
a while ago i have written a similar question:
http://groups.google.com/group/django-users/browse_thread/thread/b42239bcfb85e21f/0ec972719fbde390#0ec972719fbde390
and beside an extensible view for profiles i have now also added a few
extension mechanisms for my forum application (http://sct.
On Nov 9, 12:41 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> release, remain valid. It might sound harsh, but nothing's changed since
> then. It's very time consuming to go around again on this topic (in
> fact, it will slow down the next release, and I gather people in this
> thread want t
On Nov 9, 2:58 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> work towards 1.0. Trust me on this: the maintainers want to get it out
> the door as much as you do.
i'm sure they do .. but my "fear" (or .. guess) is that it might be
more important to be bug-free and stable for such a big miles
On Nov 8, 10:53 pm, RajeshD <[EMAIL PROTECTED]> wrote:
> I understand the concern, but how does having a 0.97 release change
> this for you? There would still be potentially backwards-incompatible
> changes moving forward from 0.97 to the next official release.
of course there will be backwards-i
Hi,
Sorry if these questions are getting boring since everyone wants to
know when the next release (and 1.0) is released .. but i haven't
found a answer by searching the forums...
After so many backward incompatible changes it would be really nice if
there would be a new django release. I want pe
hi,
i'm the author of SCT (Sphene Community Tools: http://sct.sphene.net )
- it tries to be as easy to integrate and customizable as possible
(and still to keep some kind of simplicity) - so it would be nice to
hear the requirements from people.
by default it basically looks like this: http://sct
On Aug 16, 1:42 am, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> This behaviour is valid, and will remain so. Django uses this feature
> internally in many places, especially in the serializers.
thanks, good to know :)
> Any suggestions on how to improve the documentation of this issue are
Hi,
I have a simple 'Post' model which has a 'author' ForeignKey linking
to a 'User' object - is there a way to access post.author.id without
django triggering a database query ?
- i tried to use the db column name - post.author_id .. and it
worked.. so the question remains - is this behavior i c
hi,
is there a way to extend a template with the same name, but in another
template loader ?
more specific.. it would be nice if i could customize only specific
blocks of templates by simply adding a new template loader (or another
template directory) and creating a file with the same name as the
Hi,
I've found documentation on how to make applications to work together
smoothly .. but is there also some documentation on how i could make
an application (or views of an application) extensible..
For example like in eclipse having "extension points" where 3rd party
applications could hook int
t count,
> there's zyons, myghtyboard (diamanda), SNAPboard, Sphene and maybe one
> or two I'm forgetting. Heck, my install of myghtyboard is so modded
> it's almost a branch at this point.
>
> On Feb 21, 2:15 pm, "kahless" <[EMAIL PROTECTED]> wrote:
Hi,
Since i haven't found any existing board / wiki applications which
would fit my needs and are easy enough to integrate into a custom
django project, i have created my own ..
i tried to stick to the
http://code.djangoproject.com/wiki/DosAndDontsForApplicationWriters
as much as possible.. and
n, I can use get_current_user() anywhere in my application and it
> will provide me with the current user, for some fields I even have
> something like:
>
> user = models.ForeignKey( User, default=get_current_user )
>
> I cannot take credit for this, I found it on
>
> h
layed around a little until
it worked for me: http://yourhell.com/~kahless/query_initializers_patch.diff
the usage is quite simple:
class MyModelInitializer(object):
def __init__(self, request):
self.request = request
def init_model(self, model):
model.do_init( self, self.request.user )
hi,
is there a reason why by default the render_to_response uses a Context
and not RequestContext ?
since it's the goal to make applications (and therefore templatetags &
co) as independent as possible (afaik) so it would be possible to
simply call templatetags from another application imho th
hi,
i want to make a simple template loader which loads from directories
depending on the sub-site the user requests a page from. (or probably
also from the user session - which theme he has set, etc.)
so i would need to get the current request object but haven't found a
solution for that problem
19 matches
Mail list logo
