Re: post data always empty
> > I was wondering if somebody could help me out. i'm trying to write a > simple form to create users ... however the post data always seems to > be empty. this is not the django way of doing things. Use add/change manipulators to create your forms - you are doing it by hand kg --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: post data always empty
[EMAIL PROTECTED] wrote: > I was wondering if somebody could help me out. i'm trying to write a > simple form to create users ... however the post data always seems to > be empty. > > Here's the template: > > http://code.djangoproject.com/wiki/NewbieMistakes#POSTtoviewslosesPOSTdata -- --Max Battcher-- http://www.worldmaker.net/ "I'm gonna win, trust in me / I have come to save this world / and in the end I'll get the grrrl!" --Machinae Supremacy, Hero (Promo Track) --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: post data always empty
On 4/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I was wondering if somebody could help me out. i'm trying to write a > simple form to create users ... however the post data always seems to > be empty. > [snip] Please check this document first: http://code.djangoproject.com/wiki/NewbieMistakes -- I like python! My Blog: http://www.donews.net/limodou My Django Site: http://www.djangocn.org NewEdit Maillist: http://groups.google.com/group/NewEdit --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
post data always empty
I was wondering if somebody could help me out. i'm trying to write a
simple form to create users ... however the post data always seems to
be empty.
Here's the template:
{% extends "base" %}
{% block heading %}
Welcome to Greek Life Management System, complete the information below
to create a new account.
{% endblock %}
{% block content %}
Create a new account
{% if errors %}
{{errors}}
{% endif %}
First Name:
Last Name:
E-Mail:
Username:
Password:
Confirm password:
What chapter do you belong to?
{% for option in chapters %}
{{ option.title }}
{% endfor %}
{% endblock %}
And here's the view:
from django.core.template import Context, loader
from django.utils.httpwrappers import HttpResponse,
HttpResponseRedirect
from django.models.gms import chapters, Member
from django.models.auth import users
def createAccount(request):
"""
Create new account view.
"""
t = loader.get_template('gms/CreateAccount')
errors = request
if request.POST:
data = request.POST
return HttpResponseRedirect('/member')
# Check that passwords are equal.
if data['password'] != data['confirmpassword']:
errors = 'Passwords do not match!'
else:
# Check that username does not already exist.
try:
user =
users.get_object(username__exact=data['username'])
errors = 'Username already exists!'
except:
# Validation done, create user and member
user = users.create_user(data['username'],
data['email'], data['password'])
user.first_name = data['first_name']
user.last_name = data['last_name']
user.save()
# get the chapter
chapter = chaptesr.get_object(id__exact=data['chapter'])
member = Member(chapter=chapter, user=user,
verified=False)
member.save()
# Created the user, notify the user.
return HttpResponseRedirect('/members/%s' %
user.username)
c = Context({'title': 'Create Account',
'navigation': 'nav/none',
'chapters': chapters.get_list(),
'errors': errors,
})
return HttpResponse(t.render(c))
Thanks for any help!
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Column [Datefield] cannot be null
dave.l wrote: > I have a model as follows: > > class Building(meta.Model): > survey_date = meta.DateField(null=True) > check_date = meta.DateField(null=True, blank=True) > researcher = meta.ForeignKey(Researcher) > > > I was hoping that this would let me have a blank check_date (which > would be stored as null) but enforce entry of a survey_date. But from > my admin page if I enter a survey_date (but leave the check_date blank) > I get the following on Save: > > OperationalError at /admin/coils/buildings/add/ > (1048, "Column 'check_date' cannot be null") > Request Method: POST > Request URL: http://81.3.86.154:8000/admin/coils/buildings/add/ > Exception Type: OperationalError > Exception Value: (1048, "Column 'check_date' cannot be null") > Exception Location: > /usr/lib/python2.3/site-packages/MySQLdb/connections.py in > defaulterrorhandler, line 32 > > What have I missed? This is a constraint in the database that is complaining, which means that your table in the database is not the same as the Model you provided (most likely because you made the above change after an install/sync). -- --Max Battcher-- http://www.worldmaker.net/ "I'm gonna win, trust in me / I have come to save this world / and in the end I'll get the grrrl!" --Machinae Supremacy, Hero (Promo Track) --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: basic extension of users.User
On 4/11/06, Norbert <[EMAIL PROTECTED]> wrote: Hello,I'm just starting out in really trying to get a Django app on itsfeet, even though I've played with it on and off for a couple weeks.Here's where my first cryptic error begins.I tried extend users.User in the most basic fashion I could think of:class Stakeholder(meta.Model):user = meta.ForeignKey(users.User, num_in_admin=1, \max_num_in_admin=1, unique=True, blank = True, \ null=True, default = None, edit_inline=meta.TABULAR)company = meta.CharField(maxlength=200)class META:admin = meta.Admin()def __repr__(self): return self.user.get_full_name()It seemed that the model worked sort of correctly (even though I couldnot figure out how to edit_inline a new user when creating a newstakeholder, but this not a major issue at the moment). I've done this way ( I'm sure it should be better way but this works) class Customer(models.Model): user = models.ForeignKey(User, blank = True,null=True, default = None, edit_inline= models.TABULAR,num_in_admin=1, max_num_in_admin=1, unique=True) name = models.CharField(maxlength=10,core=True) gender=models.CharField(maxlength=10,core=True) address=models.CharField(maxlength=10,core=True) def __repr__(self): return self.name def save(self): if not self.user_id: u=User(username=self.name) u.save() self.user_id=u.id super(Customer, self).save() class Admin: ordering = ['?'] --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: basic extension of users.User
On Tuesday 11 Apr 2006 9:23 am, Norbert wrote: > TemplateSyntaxError: Caught an exception while rendering. indicates a borked __repr__. Is the record being added? I think you will find that the record is added and the error comes when it tries to display the success message and list -- regards kg http://www.livejournal.com/users/lawgon tally ho! http://avsap.org.in ಇಂಡ್ಲಿನಕ್ಸ வாழ்க! --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django svn over https?
On 4/10/06, Adam <[EMAIL PROTECTED]> wrote: > > Augh, ok, sort of nevermind. Right after I hit "post", the guy who told > me our firewall wouldn't support WebDAV over http told me we have an > http proxy outside the firewall that I could use. So problem solved for > me, but it still might be useful for others with similarly draconian > firewall issues. This is an issue that should be taken up with one's system administrator(s); if you need to access a resource to do your job, yet your organization will not allow you the means to do so (even after requesting such, and especially when those means do not exactly fall into the realm of the exotic, e.g., accessing a public subversion repository over HTTP), you might want to question the sanity of your organization's policy-makers, and act accordingly. :-) Changing Django's repository to allow HTTPS access would be addressing the symptom here, not the disease; what's even worse is that enough of such concessions might convince daft system administrators that they need to clamp down on the *workarounds* (e.g., HTTPS), rather than addressing the draconian policy itself. Hopefully many such policies are less harsh than they first appear, allowing use of approved methods (e.g., proxies) when the need arises for developers. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Memory leak (db connection related?) with apache/postgres and magic-removal
On 4/10/06, Alex Brown <[EMAIL PROTECTED]> wrote: > As a follow up to this report. I tested this program on a django > install running on Mac OSX with the same versions of everything. No > memory leaks visible. So it seems to be a Windows only issue. Although > I did notice that when I built apache for OSX it uses a different > threading configuration than Windows. > > The other interesting thing was that under OSX it was like 10-100 times > slower at handling these form POSTs than the Windows setup. I haven't > closely checked the differences in apache configurations yet, so it may > be an apache config issue that is to blame for the performance. Thanks for the follow-up. I've converted a public-facing site to magic-removal in an attempt to detect any memory leaks over long processes, but I haven't seen any proof of memory leaks thus far. (I'm on Linux/Apache, which appears to make a difference, I guess...) Keep us posted! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
basic extension of users.User
Hello, I'm just starting out in really trying to get a Django app on its feet, even though I've played with it on and off for a couple weeks. Here's where my first cryptic error begins. I tried extend users.User in the most basic fashion I could think of: class Stakeholder(meta.Model): user = meta.ForeignKey(users.User, num_in_admin=1, \ max_num_in_admin=1, unique=True, blank = True, \ null=True, default = None, edit_inline=meta.TABULAR) company = meta.CharField(maxlength=200) class META: admin = meta.Admin() def __repr__(self): return self.user.get_full_name() It seemed that the model worked sort of correctly (even though I could not figure out how to edit_inline a new user when creating a new stakeholder, but this not a major issue at the moment). The problems began when I tried adding the above __repr__. The error I get when creating a new stakehold in the admin/ app is cryptic to me (I pasted it at the end of this email). How do I correctly access User variables in this model? Should I be using a different approach? I realize that it may be an obvious error, but I have gone through the documentation, and have not found anything relevant to my problem. Please help a new user from wasting many hours trying to debug this. :-) I'm using MR-branch, if that is relevant. And the reason I did not use OneToOneField or inheritance is because I've read those options are not currently the best idea for extending User. Any advice or help would be most appreciated, Norbert. Cryptic error when adding Stakeholder using admin interface: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/django/core/servers/basehttp.py", line 272, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python2.4/site-packages/django/core/servers/basehttp.py", line 615, in __call__ return self.application(environ, start_response) File "/usr/lib/python2.4/site-packages/django/core/handlers/wsgi.py", line 159, in __call__ response = self.get_response(request.path, request) File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line 109, in get_response return self.get_technical_error_response(request) File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py", line 139, in get_technical_error_response return debug.technical_500_response(request, *sys.exc_info() File "/usr/lib/python2.4/site-packages/django/views/debug.py", line 126, in technical_500_response return HttpResponseServerError(t.render(c), mimetype='text/html') File "/usr/lib/python2.4/site-packages/django/core/template/__init__.py", line 146, in render return self.nodelist.render(context) File "/usr/lib/python2.4/site-packages/django/core/template/__init__.py", line 714, in render bits.append(self.render_node(node, context)) File "/usr/lib/python2.4/site-packages/django/core/template/__init__.py", line 732, in render_node result = node.render(context) File "/usr/lib/python2.4/site-packages/django/core/template/defaulttags.py", line 112, in render nodelist.append(node.render(context)) File "/usr/lib/python2.4/site-packages/django/core/template/defaulttags.py", line 174, in render return self.nodelist_true.render(context) File "/usr/lib/python2.4/site-packages/django/core/template/__init__.py", line 714, in render bits.append(self.render_node(node, context)) File "/usr/lib/python2.4/site-packages/django/core/template/__init__.py", line 742, in render_node raise wrapped TemplateSyntaxError: Caught an exception while rendering. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Memory leak (db connection related?) with apache/postgres and magic-removal
As a follow up to this report. I tested this program on a django install running on Mac OSX with the same versions of everything. No memory leaks visible. So it seems to be a Windows only issue. Although I did notice that when I built apache for OSX it uses a different threading configuration than Windows. The other interesting thing was that under OSX it was like 10-100 times slower at handling these form POSTs than the Windows setup. I haven't closely checked the differences in apache configurations yet, so it may be an apache config issue that is to blame for the performance. Regards Alex --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Problem with threads accessing MySQL database
On 4/10/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > > kopikopiko wrote: > > Hi, > > > > I have an application set up under: > > Django 0.91 > > Windows 2000 Server > > MySQL 5.0 > > which reads scheduled events from a table then spawns threads (using > > the Thread module) to process the events and update the table. As soon > > as my threads started writing to the database I ran into MySQL error > > 2013 - 'Lost connection to MySQL server during query'. Googling led me > > to Eugene Lazutkin's blogging on the issue and patches 463 and 1442 to > > deal with the problems of the conflict over the MySQL connection > > between the threads and the original app. I applied patch 1442 as it > > seemed more recommended and the problem seemed to go away. > > #1442 was applied to trunk some time ago. Most probably you are running > an old version of Django. > > > I'm looking at how to address this by perhaps: > > 1) applying patch 1539 > > #1539 was applied to trunk as well. > > > 2) creating a new database connection in the thread (but don't know how > > to do this) > > > > Any advice would be appreciated... > > svn up your Django installation and test again. Let us know the results. The patch on #1590 was also recently applied, and it may also be a factor. -- The Pythonic Principle: Python works the way it does because if it didn't, it wouldn't be Python. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Database views
On 4/10/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 4/10/06, George Sakkis <[EMAIL PROTECTED]> wrote: > > I understand Django doesn't support database views > > (http://en.wikipedia.org/wiki/View_%28database%29) right out of the > > box, but I was wondering if there's a reasonably easy way to implement > > (or at least emulate) them. Here's an illustration of a possible API > > (compatible to the magic-removal DB API): > > Hi George, > > I seem to recall using Django with database views in the past. Django > models are simply wrappers around the database, so it should work just > fine -- the only thing is, you can't make any changes to data > (assuming you're dealing with read-only views). I researched this a bit and found that for MySQL-5.0, MS-SQL, and Oracle, you *can* update views that involve a join of multiple tables, with one limitation: You can't update multiple tables at the same time. Or to use the example, if you were updating PollChoice, you could not update values from Poll and values from Choice in the same UPDATE statement. However, since you are actually declaring what columns come from what tables in your View, it should be possible for the ORM to separate these into seperate statements. To otherwise update multiple tables in a view requires triggers and stored procedures. In PostgreSQL, it looks like you need a rule to even update one table of a view (or might only been needed for multiple table updates, I don't remember which). However, this should not be a limitation for the View class described above. -- The Pythonic Principle: Python works the way it does because if it didn't, it wouldn't be Python. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Database views
On 4/10/06, George Sakkis <[EMAIL PROTECTED]> wrote: > I understand Django doesn't support database views > (http://en.wikipedia.org/wiki/View_%28database%29) right out of the > box, but I was wondering if there's a reasonably easy way to implement > (or at least emulate) them. Here's an illustration of a possible API > (compatible to the magic-removal DB API): Hi George, I seem to recall using Django with database views in the past. Django models are simply wrappers around the database, so it should work just fine -- the only thing is, you can't make any changes to data (assuming you're dealing with read-only views). The other thing to be aware of is you'll want to manually make sure not to install a database table for your model, because it'll be hitting a view instead. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Django time-zone chaos
Hi, I am working with an app that has time issues (99% it is a Time Zone problem). I've seen some bizzar behaviour with Django that I need help with. With this model field: updated = meta.DateTimeField(auto_now=True) The time saved in my database through django running server is 4 hours ahead of the same object being edited by my python code: object.save( ) Here a few questions I have: - How could my python code object.save( ) treat the time differently than web? - Where is the time set for auto_now=True field? In PgSQL DB or in Python? Please note that I have properly set django time-zone settings to Eastern time TIME_ZONE = 'America/New_York' I even added timezone = EST to my postgresql.conf and restarted it. Regards, John --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django svn over https?
Augh, ok, sort of nevermind. Right after I hit "post", the guy who told me our firewall wouldn't support WebDAV over http told me we have an http proxy outside the firewall that I could use. So problem solved for me, but it still might be useful for others with similarly draconian firewall issues. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Problem with threads accessing MySQL database
kopikopiko wrote: > Hi, > > I have an application set up under: > Django 0.91 > Windows 2000 Server > MySQL 5.0 > which reads scheduled events from a table then spawns threads (using > the Thread module) to process the events and update the table. As soon > as my threads started writing to the database I ran into MySQL error > 2013 - 'Lost connection to MySQL server during query'. Googling led me > to Eugene Lazutkin's blogging on the issue and patches 463 and 1442 to > deal with the problems of the conflict over the MySQL connection > between the threads and the original app. I applied patch 1442 as it > seemed more recommended and the problem seemed to go away. #1442 was applied to trunk some time ago. Most probably you are running an old version of Django. > I'm looking at how to address this by perhaps: > 1) applying patch 1539 #1539 was applied to trunk as well. > 2) creating a new database connection in the thread (but don't know how > to do this) > > Any advice would be appreciated... svn up your Django installation and test again. Let us know the results. Thanks, Eugene --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Django svn over https?
Is there any chance of making the django subversion repository available over https? I'm stuck behind a firewall that will let me do svn checkouts over https, but not http. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Problem with threads accessing MySQL database
Hi, I have an application set up under: Django 0.91 Windows 2000 Server MySQL 5.0 which reads scheduled events from a table then spawns threads (using the Thread module) to process the events and update the table. As soon as my threads started writing to the database I ran into MySQL error 2013 - 'Lost connection to MySQL server during query'. Googling led me to Eugene Lazutkin's blogging on the issue and patches 463 and 1442 to deal with the problems of the conflict over the MySQL connection between the threads and the original app. I applied patch 1442 as it seemed more recommended and the problem seemed to go away. Unfortunately once I started running the application continuously (one event every 15 seconds or so) I started to get the error back at irregular intervals (as soon as 1 minute but usually within 15-20 minutes). If I comment out the database update in the thread then the error doesn't occur. I'm looking at how to address this by perhaps: 1) applying patch 1539 2) creating a new database connection in the thread (but don't know how to do this) Any advice would be appreciated... --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
will apps created with django run on a shared host that has mod_python loaded?
Or is there anything else required to run django created apps on a shared host? --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Is select_related broken in magic removal?
On 4/10/06, Dave St.Germain <[EMAIL PROTECTED]> wrote: > ...Or am I doing something wrong? > In django-trunk, select_related seems to work, but in magic-removal, I get > an empty list. It looks like the QuerySet isn't generating the joins for > related objects correctly. I'm still digging into this one, but is this a > known issue? I'm not aware of any problems with select_related...Could you paste the exact code you're using? Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Column [Datefield] cannot be null
I have a model as follows: class Building(meta.Model): survey_date = meta.DateField(null=True) check_date = meta.DateField(null=True, blank=True) researcher = meta.ForeignKey(Researcher) I was hoping that this would let me have a blank check_date (which would be stored as null) but enforce entry of a survey_date. But from my admin page if I enter a survey_date (but leave the check_date blank) I get the following on Save: OperationalError at /admin/coils/buildings/add/ (1048, "Column 'check_date' cannot be null") Request Method: POST Request URL:http://81.3.86.154:8000/admin/coils/buildings/add/ Exception Type: OperationalError Exception Value:(1048, "Column 'check_date' cannot be null") Exception Location: /usr/lib/python2.3/site-packages/MySQLdb/connections.py in defaulterrorhandler, line 32 What have I missed? Thank you, --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: advice location of site for production and devel
> 2- First thing I need to know is this: If it is a project with some > applications, the project should have a home page. From this home page, > the user can choose from running applications. In the tutorial I've > read nothing about that project home page. How can I do it? Create a > view under /home/luis/myproject? It didn't seem to work. This puzzled me too when I started with Django- it would be a useful addition to the docs if there's an elegant way of doing this. I just made a 'home' app and pointed the default url to it. It's good to have your home page within your Django project- then you use the same templates. Also, you're bound to want to put in some dynamic content sometime :) Flatpages are useful, and you can load their content dynamically in a view like this (magic-removal): from django.contrib.contenttypes.models import ContentType ... fp = FlatPage.objects.get(url='/mycontent/') and put fp.content into your context, then use it in the template. It's very useful for storing chunks of content that need to go into a dynamic page. Derek --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Multi level template inheritance
On 4/10/06, atlithorn <[EMAIL PROTECTED]> wrote:
> But it doesn't, ie. you cannot overwrite block tags from you parent's
> parent unless your parent specifies them too so you get this:
>
>
> ho ho
>
>
>
> Just wondering whether there is a solution other than sticking {%block
> ...%]{{block.super}}{%endblock%} all over the place in index.html or
> splitting things up even more with {%include/ssi%}
Hmmm. Are you sure? I'm pretty confident you *can* overwrite block
tags from your parent's parent, even if the parent doesn't specify the
blocks. I believe we have unit tests backing that up.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Feed rss and xml
On 4/10/06, coulix <[EMAIL PROTECTED]> wrote: hi i amnage to make the feed working, but when a user clic on it iwould it to be an xml file with foo.xml formal, actually now its onlyfoo so rss agregators still works but when you clic on it, t ask how to open it ect.For debugging, I did this: Index: django/utils/feedgenerator.py===--- django/utils/feedgenerator.py (revision 2116) +++ django/utils/feedgenerator.py (working copy)@@ -117,7 +117,8 @@ self.url, self.length, self.mime_type = url, length, mime_type class RssFeed(SyndicationFeed):- mime_type = 'application/rss+xml' + #mime_type = 'application/rss+xml'+ mime_type = 'text/xml' def write(self, outfile, encoding): handler = SimplerXMLGenerator(outfile, encoding) handler.startDocument() Come to think of it, it is still there, and every feed aggregator, atleast the ones I or my clients have tried, consumes this without any problem. -- Amit UpadhyayBlog: http://www.rootshell.be/~upadhyay+91-9867-359-701 --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: advice location of site for production and devel
On 4/9/06, Luis P. Mendes <[EMAIL PROTECTED]> wrote:
>
> I have the project in /home/luis/myproject. Is it for a security reason
> that it should not be placed under htdocs? or other...
Yes, that is certainly part of it. Consider your settings.py file. It
has all your DB connection settings (username, password etc). That is
not something you want in a publicly accessible area of your server.
>
> 1- I run the django server and when I do http://localhost/application
> everything runs ok;
>
> 2- First thing I need to know is this: If it is a project with some
> applications, the project should have a home page. From this home page,
> the user can choose from running applications. In the tutorial I've
> read nothing about that project home page. How can I do it? Create a
> view under /home/luis/myproject? It didn't seem to work.
If you want to create any pages generated by django, then the url for
that page needs to be added to urls.py, which would then point to your
view. See the docs for info:
http://www.djangoproject.com/documentation/url_dispatch/ In case it
isn't clear, your url pattern would be defined something like this:
urlpatterns = patterns('',
...
(r'', 'path.to.your.view'),
)
Which says that if your url is empty use the specified view. This
works great if the front page was to contain dynamic content - much
like the home page of djangoproject.com which pulls data from various
apps.
Alternatively, if you have static content which you would manually
edit occasionally, you could use flatpages for this. Simply put, if no
matches are found in urls.py, django checks for a flatpage with a
matching url and serves that if it is found. This actually sounds like
the best solution to your situation. For more on flatpages see:
http://www.djangoproject.com/documentation/flatpages/
>
> 3- Or it could be an index.html file placed under htdocs, served by
> apache with links to 'application'. For me this solution would suit my
> needs at the moment, since the home page doesn't need any dynamic
> contents. If so, how to configure both django and apache settings? and
> how can I refer back to the index.html from inside any application?
I would NOT suggest this as the first solution, but here is one
untested answer (sort of). Assuming you set up mod-python according to
the instructions in the docs, look specifically at the section:
Serving Media Files
http://www.djangoproject.com/documentation/modpython/#serving-media-files
While your index.html is not exactly a media file, you still want to
serve it the same way as pre-existing image and css files. Note the
directives in the examples that 'SetHandler None'. This
basically turns off mod_python for those locations. In your case, you
want to turn off mod_python for the url "/", but not "/foo" or "/bar"
ect. I would assume this is possible with , but have
not tested it and am not going to suggest any possible solutions
because it just doesn't feel right, even if it does work. Flatpages
would be much better in this instance.
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Modify pulldown contents in admin interface
Russell, Michael, tonecmd,
Thanks a lot for the replies.
What I've ended up doing is adding a limit_choices_to like this:
candidate = meta.ForeignKey(Candidate, limit_choices_to = {'id__in':
['1', '2']} )
Then I intercept the admin url, get the current user, and in a method
on the class that has the 'candidate' field, I get the list of ids of
candidates he has access to, and then set:
self._meta.fields[1].rel.limit_choices_to = {'id__in': result}
This dynamically updates the limit_choices_to depending on the current
user.
It isn't exactly pretty, and I'm not sure if it causes an issue with
threading (I don't know how mod_python works well enough), but it works !
I'm using the CVS trunk build.
Thanks again,
Graham.
Russell Cloran wrote:
> Hi,
>
> On Mon, 2006-04-10 at 15:36 +0100, Graham King wrote:
>> Is there a way to control the values that appear in a pulldown (a
>> ForeignKey field) on the admin interface ?
>>
>> I would like the ForeignKey to only be assignable to a subset of all
>> values.
>
> Is the limit_choices_to option suitable? It lets you limit your choices
> based on some query.
>
> http://www.djangoproject.com/documentation/model_api/#many-to-one-relationships
>
> Russell
>
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Query for "missing" information
Hi Tone,
Either I misunderstand the docs, or I misunderstand how this can be
useful to me. Or this is not particularly useful to me.
B.objects.extra(select={'foo': 'SELECT COUNT(*) FROM app_a WHERE
b_id=app_b.id'}, where=['`foo` > 0'])
generates a SQL query:
SELECT `app_b`.`id`,(SELECT COUNT(*) FROM app_a WHERE b_id=app_b.id) AS
`foo` FROM `app_b` WHERE `foo` > 0
... which MySQL says is invalid (OperationalError: (1054, "Unknown
column 'foo' in 'where clause'")).
Similarly,
B.objects.extra(select={'foo': 'SELECT COUNT(*) as c FROM app_a WHERE
b_id=app_b.id and c > 0'})
Generates:
SELECT `app_b`.`id`,(SELECT COUNT(*) as c FROM app_a WHERE b_id=app_b.id
and c > 0) AS `foo` FROM `app_b`
Which gives:
OperationalError: (1054, "Unknown column 'c' in 'where clause'")
So... I don't think I can do this with subselects (at least with
MySQL?), I need to be able to use an OUTER JOIN.
Russell
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Model module naming in m-r
On 4/10/06, Fawad Halim <[EMAIL PROTECTED]> wrote:
>
> In db/models/base.py, there is a check that goes like
>
> if re.sub('\.models$', '', mod) not in settings.INSTALLED_APPS:
>
> That kinda indicates that the models module name should end in .models.
>
> Regards
> -fawad
>
Per python (oversimplified) basics: if python finds the dir models/
which contains an __init__.py, then all files in that dir will be
imported regardless of name (they just need to be python files i.e.:
*.py). However, of python instead finds the file 'models.py', that
will be imported. Seeing models.py is importing but models/somefile.py
does not, that makes me think you are missing the __init__.py file in
your models/ dir.
Actually, I see quite a bit of confusion on this list over how python
imports. A better explaination than I could give can be found here:
http://diveintopython.org/xml_processing/packages.html
--
Waylan Limberg
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Feed rss and xml
Err, before running off into XSL land, you might want to try a few things beforehand. Why not add some CSS to your XML feed, many newer browsers will render the XML using the CSS to give a human-readable output. I'd definitely do that before getting involved with XSL transforms (you'll likely have to call an XSLT processor programme from within your view methods - not a trivial thing to do). Cheers, Tone --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Query for "missing" information
Dunno about the ORM, but the DB API exposes raw 'selects' as well; http://www.djangoproject.com/documentation/db_api/ (under 'Other Lookup Options') Cheers, Tone --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Modify pulldown contents in admin interface
If you're using magic removal, this thread outlines a nice solution; http://groups.google.com/group/django-users/browse_frm/thread/f8dace4668c0c2b1/d9ad4190912c0bd1?q=limit_choices_to=3#d9ad4190912c0bd1 Cheers, Tone --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Feed rss and xml
nice ill do it in xsl then, I ll need to - change the feed template - change the extension from foo to foo.xml. how do i do the later ? thank you --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Query for "missing" information
Hi all, I have a model (A) which has a foreign key to another (B). I wish to construct a query for all B which have an empty a_set. This is possible with SQL, using something like: SELECT b.id FROM b LEFT OUTER JOIN a ON b.id=a.b_id WHERE b.a_id IS NULL; How would I construct such a query using the Django ORM? Thanks in advance, Russell --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Modify pulldown contents in admin interface
Hi, On Mon, 2006-04-10 at 15:36 +0100, Graham King wrote: > Is there a way to control the values that appear in a pulldown (a > ForeignKey field) on the admin interface ? > > I would like the ForeignKey to only be assignable to a subset of all > values. Is the limit_choices_to option suitable? It lets you limit your choices based on some query. http://www.djangoproject.com/documentation/model_api/#many-to-one-relationships Russell --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Modify pulldown contents in admin interface
Graham King schrieb: > Dear django-users, > > Is there a way to control the values that appear in a pulldown (a > ForeignKey field) on the admin interface ? Yes, that's limit_choices_to. Search for this in the documentation to models. Michael --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Modify pulldown contents in admin interface
Dear django-users, Is there a way to control the values that appear in a pulldown (a ForeignKey field) on the admin interface ? I would like the ForeignKey to only be assignable to a subset of all values. Any help much appreciated. Graham. --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Model module naming in m-r
On Mon, April 10, 2006 09:01, James Bennett wrote:
>
> On 4/10/06, Fawad Halim <[EMAIL PROTECTED]> wrote:
>
>> I was trying to port an existing (0.91) app to the m-r branch, and
>> found that apparently, the m-r branch requires the models to reside in
>> models.py directly under the app directory
>
> The only restriction I'm aware of is that there needs to be something
> importable in Python by 'projectname.appname.models'. Whether that's a file
> called 'models.py' or a directory called 'models' is up to you; 'manage.py
> startapp' generates a single 'models.py' file, but that's not indicative
> of any restrictions on what you can do by manually creating directories
> and files.
>
> --
> "May the forces of evil become confused on the way to your house."
> -- George Carlin
My original model was in /models/.py (there is 1
app in the project, so I made the project itself the app). I ported the
model differences in .py, and tried to import
.models. in manage.py shell. I got the error
INSTALLED_APPS must contain .models. in order for
you to use this model.
I had in INSTALLED_APPS from before. Moving the model file
from .models..py to .models.py made
the import work.
In db/models/base.py, there is a check that goes like
if re.sub('\.models$', '', mod) not in settings.INSTALLED_APPS:
That kinda indicates that the models module name should end in .models.
Regards
-fawad
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Model module naming in m-r
On 4/10/06, Fawad Halim <[EMAIL PROTECTED]> wrote: > I was trying to port an existing (0.91) app to the m-r branch, and found > that apparently, the m-r branch requires the models to reside in > models.py directly under the app directory The only restriction I'm aware of is that there needs to be something importable in Python by 'projectname.appname.models'. Whether that's a file called 'models.py' or a directory called 'models' is up to you; 'manage.py startapp' generates a single 'models.py' file, but that's not indicative of any restrictions on what you can do by manually creating directories and files. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: extend User in m-r
Bryan,
this won't work either, because when you try to save the user using
admin you will have this kind of error:
Request Method: POST
Request URL:http://localhost:8000/admin/auth/user/40/
Exception Type: TypeError
Exception Value:Cannot resolve keyword 'name' into field
Exception Location:
c:\soft\python24\lib\site-packages\django\db\models\query.py in
lookup_inner, line 764
'name' being the unique property defined for my related object:
name = models.CharField(_('name'),maxlength=200,unique=True,core=True)
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Multi level template inheritance
Template inheritance question: Let's say I have the following
templates,
#1.base.html
{%block start%}{%endblock%}
{%block stuff%}hey hey{%endblock%}
{%block stop%}{%endblock%}
#2. index.html
{%extends "base"%}
{%block stuff%}ho ho{%endblock%}
#3. different.html
{%extends "index"%}
{%block start%}{%endblock%}
{%block stop%}{%endblock%}
I would expect different.html to render like this:
ho ho
But it doesn't, ie. you cannot overwrite block tags from you parent's
parent unless your parent specifies them too so you get this:
ho ho
Just wondering whether there is a solution other than sticking {%block
...%]{{block.super}}{%endblock%} all over the place in index.html or
splitting things up even more with {%include/ssi%}
--~--~-~--~~~---~--~~
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.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---
Re: Feed rss and xml
On 4/10/06, coulix <[EMAIL PROTECTED]> wrote: > hi i amnage to make the feed working, but when a user clic on it i > would it to be an xml file with foo.xml formal, actually now its only > foo so rss agregators still works but when you clic on it, t ask how to > open it ect. This is the intended behavior for feeds; "viewing it in the browser", unless the browser has a built-in feed reader, would mean displaying the raw unstyled XML, and that's likely to be even more confusing to a user than the prompt displayed for a feed which uses the correct media type. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Django + fastCGI + bluehost
James wrote: >> I have django running on my bluehost account with fcgi. The best notes on how to get >> things running I have found are here: >> >> http://wiki.dreamhost.com/index.php/Django >> >> Bluehost is setup pretty much the same as dreamhost. I recommend >> Bluehost for the price and support. Thanks for the tip! I'll be moving to Bluehost very soon, then. Gabor wrote: > hi, could i ask you some questions regarding bluehost: > > - python version > - do they offer postgresql (form their webpage it seems so. just wanted > to make sure) > - do i have to buy at least an one-year subscription? can't i just pay > for the first month at the beginning? (it seems that you either buy a > 12month subscription for 7.95$/month, or a 24month one for 6.95$/month) > > thanks, > gabor I guess you'll have to ask Bluehost about that! -- Carlos Yoder [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
Re: Meet error in "Writing your first Django app, part 1"
On Sunday 09 Apr 2006 12:06 pm, Holio wrote: > `python manage.py init polls' python manage.py install polls -- regards kg http://www.livejournal.com/users/lawgon tally ho! http://avsap.org.in ಇಂಡ್ಲಿನಕ್ಸ வாழ்க! --~--~-~--~~~---~--~~ 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.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~--~~~~--~~--~--~---
