Totally agree with you about Viktor tutorial.
Finally a teacher that uses diagrams to show newbies how models are related etc
I followed a tutorial on udemy before, I learned quit a lot.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubs
> The only criticism I have seen of lighttpd is that is has been a long
> time since last release and that it can leak memory. Don't know how
> valid that is, so I could be generating my own FUD here. :-)
Well. I was running it for more than a year without a restart at some
stage and I didn't not
currently running lighttpd which has a fair bit of config
that I don't want to move, I'm going to probably run that in front of
apache rather than nginx. (at least for now and assuming it "just
works")
Le Roux
--~--~-~--~~~---~--~~
You received this
> If it is to bring down application for maintenance, seems like it
> would be easier to use Apache/mod_wsgi in daemon mode.
I'll give mod_wsgi a go. To be honest I never looked at it before
simply because it is tied to apache. But if it can easily do
everything I need using a reasonable amount o
I'm trying to keep my django powered cms online even when I have to
restart the app or take it down for maintenance.
My rendered pages are generally quite cacheable and they only change
if someone content manages a page or someone comments, etc. which
happens relatively rarely.
I have a very cru
I actually just tried that, but I'm getting import errors. Probably
because I am importing from myapp.something.module..
Putting code in settings.py just seems dodgy.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Actually, no. That didn't really work. Now manage.py seems even more
confused.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.co
Aah. It is because of this chicken and egg scenario.. manage.py adds
your project's dir to the path after it imports your settings module.
So when the settings module is being imported your project is not in
the path yet, so you cannot import from
myproject.some_package.some_module..
I now added
sking if there is a place where I can put code that will
always run when a django process executes and before any save() methods
are called..
Le Roux
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django us
o way of
"making it idiot proof"... ;)
On 20/07/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 7/19/06, Le Roux <[EMAIL PROTECTED]> wrote:
> >
> > If I do something like MyModel.objects.filter(id__in=[1, 2,
> > 3]).delete(), it doesn't look
the delete() method in the model to delete the
associated file(s), but it looks like that won't cut it.
If there's no easy way to override the bulk delete, is there at least a
way to stop the QuerySet's delete from executing?
Le Roux
--~--~-~--~~~---~-
I recently had a similar problem and ended up just writing some custom
sql (see
http://www.djangoproject.com/documentation/model_api/#executing-custom-sql)
because I can only think of doing this useing a group by clause.
(unless you just want the category ids, then you can do a SELECT
distinct cat
Aah thanks. I actually saw that function, noticed that it returns
dictionaries, but didn't notice the fact that you can pass in the
fields you want as parameters..
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Dj
Is there any way of telling the db api to not return certain fields? I
want to get a list of all the news articles for a specific year and I
don't need the big fields like the body text. I can't find anything in
the documentation, but thought that maybe someone else already dealt
with it.
I know
innick <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2006-07-06 at 10:31 +, Le Roux wrote:
> > Looks like I fixed it now. Here's a patch:
> >
> > django_src/django/forms/__init__.py:
> >
> > --- __init__.py (revision 3278)
> > +++ __init__.py (workin
http://code.djangoproject.com/ticket/2300
http://code.djangoproject.com/attachment/ticket/2300/django_forms__init__.diff
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, s
oops. that manipulator.save() bit is a bit buggy (I changed it after I
pasted to give returnValue a more meaningful name and then didn't
change all the occurrances) but it works here ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
Looks like I fixed it now. Here's a patch:
django_src/django/forms/__init__.py:
--- __init__.py (revision 3278)
+++ __init__.py (working copy)
@@ -53,6 +53,7 @@
def get_validation_errors(self, new_data):
"Returns dictionary mapping field_names to error-message
lists"
+self
aah sorry.. my reply was to your first reply ;) I'll re-read everything
and then think again ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users
I'm referring to CheckboxSelectMultipleField and your code snippet is
for CheckboxField...
I'm going to do an svn up just incase and think about it a bit more..
maybe I'm missing something. As far as I can tell the rendering works
fine. The value is just completely blank "on the other side" after
lly uses prepare and since the formfield
generally doesn't work it probably means it is not widely used ;)
Le Roux
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to thi
Cool. Thanks a lot. I'll try that out when I get home. It is definitely
the cleanest solution by far.
I thought about that and actually started implementing it, but then I
realised that it is not very maintainable and things will be too
coupled. (I like using the development server for development and I
would like to try and deploy on lighttpd)
Plus then every resource effectively has two urls wh
Thanks. I'll do that. It just feels like that type of thing should
happen outside of the view (and come to the view as a parameter). The
other thing is that _all_ my views will need this and to me that just
feels a bit dirty. I guess it is probably the best way, though.
l the
subdomains, so how do I extract the subdomain name and send it to my
view? I figure this should be possible with the middleware, but
where/how?
Le Roux
t containing of wiki pages for that wiki only)
Is this possible? Or can you suggest an alternative? If there is
nothing to do this, then I don't mind adding something. Please just
point me in the right direction.. I don't really know my way around
Django's code yet ;)
Le Roux
Thanks! wow, that was quick!
I can see the query is selecting a lot more stuff, but when I do a
self.get_owner() inside my function, it still run a query.. self.owner
is not already set either.
Surely it shouldn't run the query?
Le Roux
t a little
plus next to each wiki for adding a wikipage. This will then take you
to the wikipage add form and have the correct wiki preselected.
Maybe this is already possible, but I just can't find it ;)
Le Roux
_related=True
to the lookup for the listing? Then I don't have to do a query for
each row in the listing and I can just somehow use the owner object
directly.
Le Roux
29 matches
Mail list logo
