Nabble - Django

flatpages not finding site_media

2009-11-10T23:50:06Z

I'm trying to use some flatpages for static content and I don''t
understand why they keep failing to load media files. I have my
template_dirs defined, media_root and media_url - when used in
template does not resolve to media_root i.e., template contains:

<link rel="stylesheet" href="{{ media_url }}css/base.css" type="text/
css" media="screen" title="Base Styles" charset="utf-8">

results in:

Failed to load source for: http://127.0.0.1:8000/about/css/base.css

MEDIA_ROOT = '/Users/neridaj/django-templates/neridaj/'
MEDIA_URL = '/site_media/'
TEMPLATE_DIRS = (
'/Users/neridaj/django-templates/neridaj/'
)

The default template renders but without any of the css.

Thanks,

J
--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: Uploading and using images in a database application

2009-11-10T23:37:43Z

Adrian

Does the Photologue app store the image references in the database?

On Nov 5, 6:58 pm, adrian <adrian...@...> wrote:

> The easiest way is to use the Photologue application.
> It has done most of the work for you.
>
> On Nov 5, 9:53 am, bruno desthuilliers <bruno.desthuilli...@...>
> wrote:
>
> > On 3 nov, 16:02, derek <gamesb...@...> wrote:
>
> > > Given that I am a "wet behind the ears" newbie, maybe I should not be
> > > attempting this, but...
>
> > Attempts at thing we don't yet fully grasp can be a good way to
> > learn.
>
> > > I need some simple and straightforward guidance on
> > > uploading and using images in a simple database application, which (so far)
> > > only uses the admin interface.
>
> > > I working on my development machine (i.e. no Apache integration as yet).
>
> > > The use case is not that complex. If I have an "Event" object, with which I
> > > want to associate a number of images (typically, photos taken by people at
> > > that event), then I also need an "EventImage" object, with the event.id as
> > > the foreign key.
>
> > > So, the models look like:
>
> > > class Event(models.Model):
> > > id = models.AutoField(primary_key=True)
>
> > Hint : if you leave this previous line out, Django will automagically
> > add this very same field to your model !-)
>
> > > date_time = models.DateTimeField()
> > > title = models.CharField(unique=True,max_length=250)
>
> > > class EventImage(models.Model):
> > > id = models.AutoField(primary_key=True)
> > > caption = models.CharField(unique=True,max_length=10)
> > > title = models.CharField(max_length=250)
> > > event = models.ForeignKey(Event)
> > > image = models.ImageField(upload_to='photos')
>
> > > What I have gathered so far, from browsing articles and snippets and Q&A, is
> > > that I also need:
>
> > > 1.to add/change settings.py:
>
> > > MEDIA_ROOT = '/home/blah/blah/mysite/media/'
> > > MEDIA_URL = 'http://127.0.0.1:8000/media/'
> > > ADMIN_MEDIA_PREFIX = '/media/'
>
> > Using the same path component for both the static medias and the admin
> > media usually leads to unexpected results. Either change your static
> > medias component path to something else or - way simplier -, change
> > the ADMIN_MEDIA_PREFIX (here we canonically set it to 'admin-media').
>
> > > STATIC_DOC_ROOT = '/home/blah/blah/mysite/media/'
>
> > > 2. add the following to the start of urls.py:
>
> > > from django.conf import settings
>
> > > 3. add the following to the end of urls.py:
>
> > > if settings.DEBUG:
> > > urlpatterns += patterns('',
> > > (r'^static/(?P<path>.*)$', 'django.views.static.serve',
> > > {'document_root': settings.STATIC_DOC_ROOT}),
> > > )
>
> > This url pattern is not consistant with the your MEDIA_URL settings. A
> > good way to avoid this kind of problems is to follow the SPOT rule:
>
> > ### in settings.py
> > import os
>
> > PROJECT_PATH = os.path.dirname(os.path.abspath(__file__))
> > SITE_URL = "http://127.0.0.1:8000"
>
> > MEDIA_DIR = "media"
> > MEDIA_ROOT = os.path.join(PROJECT_PATH, MEDIA_DIR)
> > MEDIA_URL = "%s/%s/" % (SITE_URL, MEDIA_DIR)
>
> > ADMIN_MEDIA_PREFIX = '/admin-media/'
>
> > # decouple this from the DEBUG flag - you may want to
> > # set DEBUG to true in preproduction
> > # (ie, running behind apache or another web server)
> > DEV_SERVER = True
>
> > ### in urls.py
> > from django.conf import settings
>
> > # urls here...
>
> > if settings.DEV_SERVER:
> > urlpatterns += patterns('',
> > (r'^%s/(?P<path>.*)$' % setting.MEDIA_DIR,
> > 'django.views.static.serve',
> > {'document_root': settings.MEDIA_ROOT}),
> > )
>
> > > (I have also tried variations on the above, such as:
> > > (r'^media/(?P<path>.*)$', 'django.views.static.serve',
>
> > which may have worked, minus the conflict between MEDIA_URL and
> > ADMIN_MEDIA_PREFIX
>
> > > and
> > > (r'%s(?P<path>.*)' % settings.MEDIA_URL[1:],
>
> > MEDIA_URL is a string, so MEDIA_URL[1:] is the same string minus the
> > first character, ie, in your case : "ttp://127.0.0.1:8000/media/".
> > Probably not what you expected !-)
>
> > > 'django.views.static.serve',
> > > {'document_root': settings.MEDIA_ROOT}),
> > > )
>
> > > but in all cases, although the file does get uploaded and appears in the
> > > '/home/blah/blah/mysite/media/photos/' directory, when I click on the link -
> > > which is shown as
>
> > >http://127.0.0.1:8000/media/photos/test.jpg
>
> > > I get a "Page not found: /media/photos/test.jpg"
>
> > > This seems like a simple thing to fix - but not for me?
>
> > cf above.
>
> > > Any help to fix this is appreciated, as is any guidance on what will need to
> > > change once this project needs to run under Apache...
>
> > If you're careful to use the "medias" context processor and
> > {{ MEDIA_URL }} in your templates, you shouldn't have to do much more
> > than update your settings.py appropriately. But anyway - first fix
> > your development setup.
>
>

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: Uploading and using images in a database application

2009-11-10T23:36:22Z

Bruno

All the help is much appreciated - its working now, and I need to
spend time to understand all the changes.

On Nov 5, 5:53 pm, bruno desthuilliers <bruno.desthuilli...@...>
wrote:

> On 3 nov, 16:02, derek <gamesb...@...> wrote:
>
> > Given that I am a "wet behind the ears" newbie, maybe I should not be
> > attempting this, but...
>
> Attempts at thing we don't yet fully grasp can be a good way to
> learn.
>
> > I need some simple and straightforward guidance on
> > uploading and using images in a simple database application, which (so far)
> > only uses the admin interface.
>
> > I working on my development machine (i.e. no Apache integration as yet).
>
> > The use case is not that complex. If I have an "Event" object, with which I
> > want to associate a number of images (typically, photos taken by people at
> > that event), then I also need an "EventImage" object, with the event.id as
> > the foreign key.
>
> > So, the models look like:
>
> > class Event(models.Model):
> > id = models.AutoField(primary_key=True)
>
> Hint : if you leave this previous line out, Django will automagically
> add this very same field to your model !-)
>
>
>
> > date_time = models.DateTimeField()
> > title = models.CharField(unique=True,max_length=250)
>
> > class EventImage(models.Model):
> > id = models.AutoField(primary_key=True)
> > caption = models.CharField(unique=True,max_length=10)
> > title = models.CharField(max_length=250)
> > event = models.ForeignKey(Event)
> > image = models.ImageField(upload_to='photos')
>
> > What I have gathered so far, from browsing articles and snippets and Q&A, is
> > that I also need:
>
> > 1.to add/change settings.py:
>
> > MEDIA_ROOT = '/home/blah/blah/mysite/media/'
> > MEDIA_URL = 'http://127.0.0.1:8000/media/'
> > ADMIN_MEDIA_PREFIX = '/media/'
>
> Using the same path component for both the static medias and the admin
> media usually leads to unexpected results. Either change your static
> medias component path to something else or - way simplier -, change
> the ADMIN_MEDIA_PREFIX (here we canonically set it to 'admin-media').
>
> > STATIC_DOC_ROOT = '/home/blah/blah/mysite/media/'
>
> > 2. add the following to the start of urls.py:
>
> > from django.conf import settings
>
> > 3. add the following to the end of urls.py:
>
> > if settings.DEBUG:
> > urlpatterns += patterns('',
> > (r'^static/(?P<path>.*)$', 'django.views.static.serve',
> > {'document_root': settings.STATIC_DOC_ROOT}),
> > )
>
> This url pattern is not consistant with the your MEDIA_URL settings. A
> good way to avoid this kind of problems is to follow the SPOT rule:
>
> ### in settings.py
> import os
>
> PROJECT_PATH = os.path.dirname(os.path.abspath(__file__))
> SITE_URL = "http://127.0.0.1:8000"
>
> MEDIA_DIR = "media"
> MEDIA_ROOT = os.path.join(PROJECT_PATH, MEDIA_DIR)
> MEDIA_URL = "%s/%s/" % (SITE_URL, MEDIA_DIR)
>
> ADMIN_MEDIA_PREFIX = '/admin-media/'
>
> # decouple this from the DEBUG flag - you may want to
> # set DEBUG to true in preproduction
> # (ie, running behind apache or another web server)
> DEV_SERVER = True
>
> ### in urls.py
> from django.conf import settings
>
> # urls here...
>
> if settings.DEV_SERVER:
> urlpatterns += patterns('',
> (r'^%s/(?P<path>.*)$' % setting.MEDIA_DIR,
> 'django.views.static.serve',
> {'document_root': settings.MEDIA_ROOT}),
> )
>
> > (I have also tried variations on the above, such as:
> > (r'^media/(?P<path>.*)$', 'django.views.static.serve',
>
> which may have worked, minus the conflict between MEDIA_URL and
> ADMIN_MEDIA_PREFIX
>
> > and
> > (r'%s(?P<path>.*)' % settings.MEDIA_URL[1:],
>
> MEDIA_URL is a string, so MEDIA_URL[1:] is the same string minus the
> first character, ie, in your case : "ttp://127.0.0.1:8000/media/".
> Probably not what you expected !-)
>
> > 'django.views.static.serve',
> > {'document_root': settings.MEDIA_ROOT}),
> > )
>
> > but in all cases, although the file does get uploaded and appears in the
> > '/home/blah/blah/mysite/media/photos/' directory, when I click on the link -
> > which is shown as
>
> >http://127.0.0.1:8000/media/photos/test.jpg
>
> > I get a "Page not found: /media/photos/test.jpg"
>
> > This seems like a simple thing to fix - but not for me?
>
> cf above.
>
> > Any help to fix this is appreciated, as is any guidance on what will need to
> > change once this project needs to run under Apache...
>
> If you're careful to use the "medias" context processor and
> {{ MEDIA_URL }} in your templates, you shouldn't have to do much more
> than update your settings.py appropriately. But anyway - first fix
> your development setup.

From forum: django-users

Re: annotation with filter issue (left join needed)

2009-11-10T23:08:29Z

It seems that you're right :( raw SQL takes away most of benefits of ORM

2009/11/10 akaariai <akaariai@...>

On Nov 10, 8:29 am, Михаил Лукин <mihail.lu...@...> wrote:
> Well, I didn't find solution yet. Except that filter condition must be
> placed in LEFT OUTER JOIN ... ON ( <here> ), but i'm not sure if it's
> possible with Django ORM. I notices that Aggregate base class takes 'extra'
> argument in its constructor, but I'm not sure how to use it for such
> purpose.

Django can not handle left joins where the filter conditions need to
be in the ON clause of the join. The comment for function join in
django.db.models.sql clearly states this.

So if you really need to place the filter condition on the left outer
join, then there is nothing you can do except use raw SQL.

--
regards,
Mihail

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: request.POST['value'] cannot get value, 500 error

2009-11-10T23:06:19Z

Does

request.POST['value'][0]['LastName']

work?

It looks like your post data has an array (keyed as 'value') of dicts.

You might also consider using Firebug (or something similar) to inspect the http requests and responses when you are developing.

Regards,

Tamas

On Wed, Nov 11, 2009 at 2:38 PM, robinne <developer@...> wrote:

I am posting data from a form to a django view. The form is created
using inputEx (a YUI-like interface). The form gets created much like
you create a YUI form and you include names for all your fields in
javascript. It is javascript that creates the form on the page.

I am able to load database data from the django view into my form
fields (sending json string to UI), but when I post I cannot access
individual posted values, even though I can see that the
'request.POST' is getting posted to the django view. The request.POST
looks something like <QueryDict:{u'value':
[u'{"FirstName":"Mary","LastName":"Smith"...etc]}>

When trying to access a value by using...

def MemberInfo(request, member_id):
if request.method == "POST":
print request.POST
try:
print request.POST['LastName'] #ERROR

...
error message is:
"POST /MemberInfo/1 HTTP/1.1" 500 54476

any ideas?

From forum: django-users

Template not displaying

2009-11-10T23:04:33Z

Hi all, am using xampp as webserver with django 1.1,when i access the
browser the template does not work. The media is in
c:/xampp/htdocs/adc/media/ where i put the css,img and js folders. I
set admin_media_prefix='http:/127.0.0.1/adc/media/' the same to
media_url. The template is at c:/xampp/htdocs/adc/templates/. Please
any idea on how to make the templates working?

--
Sent from my mobile device

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: [Django] #5446: New model fields for languages and countries at least

2009-11-10T22:53:42Z

#5446: New model fields for languages and countries at least
----------------------------------------------------------+-----------------
Reporter: Raphaël Hertzog <raphael@...> | Owner: marinho
Status: reopened | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords: feature_request
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------------------+-----------------
Comment (by idris):

I suggest adding a slug to the COUNTRIES list, as it would be nice to be
able to use pretty url's based on a CountryField, like /afghanistan/ or
/brazil/

--
Ticket URL: <http://code.djangoproject.com/ticket/5446#comment:19>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

request.POST['value'] cannot get value, 500 error

2009-11-10T22:38:27Z

I am posting data from a form to a django view. The form is created
using inputEx (a YUI-like interface). The form gets created much like
you create a YUI form and you include names for all your fields in
javascript. It is javascript that creates the form on the page.

I am able to load database data from the django view into my form
fields (sending json string to UI), but when I post I cannot access
individual posted values, even though I can see that the
'request.POST' is getting posted to the django view. The request.POST
looks something like <QueryDict:{u'value':
[u'{"FirstName":"Mary","LastName":"Smith"...etc]}>

When trying to access a value by using...

def MemberInfo(request, member_id):
if request.method == "POST":
print request.POST
try:
print request.POST['LastName'] #ERROR

...
error message is:
"POST /MemberInfo/1 HTTP/1.1" 500 54476

any ideas?

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: [Django] #12146: Canada localflavor: postal code validation too lax

2009-11-10T21:52:57Z

#12146: Canada localflavor: postal code validation too lax
-------------------------------------------------+--------------------------
Reporter: paulschreiber | Owner: nobody
Status: new | Milestone: 1.2
Component: django.contrib.localflavor | Version: 1.1
Resolution: | Keywords: canada postal code
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------------+--------------------------
Changes (by agabel):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0

Comment:

I'm having some trouble with the wording of the wikipedia article. "The
letters W and Z are used, but are not currently used as the first letter."
Does this mean the first letter of the Postal Code, (Zxx xxx) or does it
apply to the first letter in both the FSA and the LDU (Zxx Zxx)?

I was unable to find any relevant information after a quick search. I
would like to see another source validating this besides wikipedia.

--
Ticket URL: <http://code.djangoproject.com/ticket/12146#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Re: [Django] #12104: Object->object lookup fails in blocktrans

2009-11-10T21:04:33Z

#12104: Object->object lookup fails in blocktrans
-------------------------------------------+--------------------------------
Reporter: philipn | Owner: nobody
Status: reopened | Milestone:
Component: Internationalization | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by philipn):

* status: closed => reopened
* resolution: invalid =>

Comment:

If this is to keep translations simple then that makes sense, especially
considering blocktrans doesn't allow for other blocks inside it.

Adding support for other block tags inside of blocktrans seems easy enough
to add, though (using the same idea as my patch -- executing a template
rendering).

But, unlike other blocks in blocktrans, this kind of variable access
doesn't trigger an error message.

I've attached a patch that causes an error to be displayed when you try
and use complex variable lookups inside a blocktrans block.

If we did decide to allow for variable.attr syntax then it would probably
be better to use django.template's Variable class to look up the
variable's values rather than the context-dictionary-key approach used in
the code currently.

I guess it's also worth noting that the current blocktrans variable lookup
behaviour will throw a keyerror for{{{ {{ variable_that_isnt_in_context }}
}}}when templates normally do not. With this in mind it really seems like
the right thing to do is to replace the lookup behaviour with
{{{Variable(..).resolve()}}}. I've attached a patch that does this, as
well.

--
Ticket URL: <http://code.djangoproject.com/ticket/12104#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Re: tiny_mce TypeError

2009-11-10T20:50:43Z

I'm using 1.2 pre-alpha, I tried pasting that code in, again, but no
dice.

On Nov 10, 8:06 pm, James Bennett <ubernost...@...> wrote:

> On Tue, Nov 10, 2009 at 9:47 PM, neridaj <neri...@...> wrote:
> > I'm just following "Practical Django Projects" and was curious if
> > anyone else was able to fix a TypeError when trying to add tiny_mce to
> > the admin for flatpages, or is this something buried in the
> > tiny_mce.js file?
>
> Compare to this, which is the canonical version (and which worked
> locally for me on 1.1 when I committed it):
>
> http://bitbucket.org/ubernostrum/practical-django-projects/src/tip/cm...
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."

From forum: django-users

Re: How to handle this race condition?

2009-11-10T20:35:03Z

Thank you.

On Nov 10, 10:03 pm, Tamas Szabo <szab...@...> wrote:

> You can inspect the rowcount attribute of the cursor object after you
> executed your update.
> rowcount returns the number of rows affected by your update, so it will be 1
> if your where condition was true.
>
> On Wed, Nov 11, 2009 at 10:04 AM, Continuation <selforgani...@...>wrote:
>
>
>
> > > Would something like
>
> > > UPDATE bid = new_bid WHERE id = id and bid < new_bid
>
> > > work for you?
>
> > This is a great idea.
>
> > One question is, how do I know whether bid has been updated to new_bid
> > or not (ie. how to tell whether the conditional test bid < new_bid is
> > true or not)?

From forum: django-users

Re: tiny_mce TypeError

2009-11-10T20:06:44Z

On Tue, Nov 10, 2009 at 9:47 PM, neridaj <neridaj@...> wrote:
> I'm just following "Practical Django Projects" and was curious if
> anyone else was able to fix a TypeError when trying to add tiny_mce to
> the admin for flatpages, or is this something buried in the
> tiny_mce.js file?

Compare to this, which is the canonical version (and which worked
locally for me on 1.1 when I committed it):

http://bitbucket.org/ubernostrum/practical-django-projects/src/tip/cms/templates/admin/flatpages/flatpage/change_form.html

--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: [Django] #3665: select_related() should generate LEFT JOINs for foreign keys with null=True

2009-11-10T19:58:28Z

#3665: select_related() should generate LEFT JOINs for foreign keys with null=True
-----------------------------------------+----------------------------------
Reporter: semenov@... | Owner: mtredinnick
Status: closed | Milestone:
Component: Core framework | Version: 1.1
Resolution: duplicate | Keywords: orm select_related left join
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------+----------------------------------
Changes (by Alex):

* status: reopened => closed
* resolution: => duplicate

Comment:

This ticket was closed over 2 years ago, please do not reopen it. If you
think there is a new bug please file a new bug.

--
Ticket URL: <http://code.djangoproject.com/ticket/3665#comment:7>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Re: [Django] #3665: select_related() should generate LEFT JOINs for foreign keys with null=True

2009-11-10T19:56:53Z

#3665: select_related() should generate LEFT JOINs for foreign keys with null=True
-----------------------------------------+----------------------------------
Reporter: semenov@... | Owner: mtredinnick
Status: reopened | Milestone:
Component: Core framework | Version: 1.1
Resolution: | Keywords: orm select_related left join
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------+----------------------------------
Changes (by retrogradeorbit):

* status: closed => reopened
* version: SVN => 1.1
* resolution: duplicate =>

Comment:

This ticket is still not fixed as it was never really a duplicate of
#3592. The behavior explained in this ticket still persists in the most
recent versions of Django and this ticket describes the problem exactly.
In fact the best description of the problem from the ticket is:

"select_related() should always use LEFT JOINs for all nullable foreign
keys. The recursion should not proceed to these fields."

--
Ticket URL: <http://code.djangoproject.com/ticket/3665#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

tiny_mce TypeError

2009-11-10T19:47:13Z

Hello,

I'm just following "Practical Django Projects" and was curious if
anyone else was able to fix a TypeError when trying to add tiny_mce to
the admin for flatpages, or is this something buried in the
tiny_mce.js file?

(r'^tiny_mce/(?P<path>.*)$', 'django.views.static.serve',
{ 'dcument_root': '/Users/username/src/tinymce/jscripts/tiny_mce' }),

<script type="text/javascript" src="/tiny_mce/tiny_mce.js"></script>
<script type="text/javascript">
tinyMCE.init({
mode: "textareas",
theme: "simple"
});
</script>

Thanks,

J
--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: [Django] #9447: ifequal should be chainable(and,or)

2009-11-10T19:11:17Z

#9447: ifequal should be chainable(and,or)
---------------------------------------------+------------------------------
Reporter: hybrid.basis@... | Owner: nobody
Status: new | Milestone:
Component: Template system | Version: 1.0
Resolution: | Keywords: ifequal,and,or
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by anonymous):

critical issue !

--
Ticket URL: <http://code.djangoproject.com/ticket/9447#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Re: How to handle this race condition?

2009-11-10T19:03:41Z

You can inspect the rowcount attribute of the cursor object after you executed your update.
rowcount returns the number of rows affected by your update, so it will be 1 if your where condition was true.

On Wed, Nov 11, 2009 at 10:04 AM, Continuation <selforganized@...> wrote:

> Would something like
>
> UPDATE bid = new_bid WHERE id = id and bid < new_bid
>
> work for you?

This is a great idea.

One question is, how do I know whether bid has been updated to new_bid
or not (ie. how to tell whether the conditional test bid < new_bid is
true or not)?

From forum: django-users

Re: How to handle this race condition?

2009-11-10T18:04:59Z

> Would something like
>
> UPDATE bid = new_bid WHERE id = id and bid < new_bid
>
> work for you?

This is a great idea.

One question is, how do I know whether bid has been updated to new_bid
or not (ie. how to tell whether the conditional test bid < new_bid is
true or not)?

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: How to handle this race condition?

2009-11-10T17:25:33Z

Anyways, as concurrency is hard and taking row level locks is cheap
and easy way to get the concurrency right I would suggest you use the
select for update method. Also, this way you will avoid the need to
retry failed transactions because of concurrent updates.

IMHO, both approaches are valid and have their own advantages and disadvantages.
I don't think that we have enough information to make a suggestion.
What works best for the situation is for the OP to decide.

Regards,

Tamas

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: datetime problems with Django application

2009-11-10T16:57:46Z

There may be another application setting the time zone, but my question still remains as to why the admin page is getting the correct time but the view is not.

Brian

On Tue, Nov 10, 2009 at 7:45 PM, Graham Dumpleton <graham.dumpleton@...> wrote:

On Nov 11, 10:41 am, BEC <chapma...@...> wrote:
> I have a Django application running with mod_python on Apache. In
> settings.py I have set TIME_ZONE="America/New_York". Within my
> application I verify that os.environ['TZ'] is indeed set to this
> value. Within my view.py I use datetime.datetime.now() to create a
> time stamp that is stored in a model as a DateTimeField and viewed on
> a rendered html page.
>
> However, the times that I generate in my view are all off from what
> they should be by five hours. I've changed the time zone around
> "America/Chicago", "America/Anchorage" etc. no matter what I set
> TIME_ZONE to, I get the same wrong time (5 hours off).
>
> If I go to the admin page and use the change entry page to modify the
> values stored in the database, the Time now link gives the correct
> time?
>
> Any idea on what is going on here? I'm particularly perplexed as to
> why the admin page and my view are giving different times.

Do you run other Python or PHP applications in the same Apache? If you
do they likely have conflicting time zone requires.

The problem here is that TZ is a process wide setting and can only be
set to one value at a time. Thus, whatever application got to set it
last will take precedence.

See:

http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Timezone_and_Locale_Settings

Use mod_wsgi daemon mode or fastcgi solutions, both of which can run
applications in their own processes if you are being afflicted with
this problem.

Graham

From forum: django-users

Re: datetime problems with Django application

2009-11-10T16:45:13Z

On Nov 11, 10:41 am, BEC <chapma...@...> wrote:

> I have a Django application running with mod_python on Apache. In
> settings.py I have set TIME_ZONE="America/New_York". Within my
> application I verify that os.environ['TZ'] is indeed set to this
> value. Within my view.py I use datetime.datetime.now() to create a
> time stamp that is stored in a model as a DateTimeField and viewed on
> a rendered html page.
>
> However, the times that I generate in my view are all off from what
> they should be by five hours. I've changed the time zone around
> "America/Chicago", "America/Anchorage" etc. no matter what I set
> TIME_ZONE to, I get the same wrong time (5 hours off).
>
> If I go to the admin page and use the change entry page to modify the
> values stored in the database, the Time now link gives the correct
> time?
>
> Any idea on what is going on here? I'm particularly perplexed as to
> why the admin page and my view are giving different times.

Do you run other Python or PHP applications in the same Apache? If you
do they likely have conflicting time zone requires.

The problem here is that TZ is a process wide setting and can only be
set to one value at a time. Thus, whatever application got to set it
last will take precedence.

See:

http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Timezone_and_Locale_Settings

Use mod_wsgi daemon mode or fastcgi solutions, both of which can run
applications in their own processes if you are being afflicted with
this problem.

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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: A simple database project

2009-11-10T16:35:28Z

On Wednesday 11 Nov 2009 5:51:00 am Zeynel wrote:
> So I want to enter in the search box "Lawyer1" and in the result page
> I want to see "Lawyer1 knows Lawyer2"
>
if your school is a foreign key (I think it is) you need a related name to
search for that. Check out ModelAdmin.search_fields in the docs. Not sure that
this is what you are looking for though.
--
regards
Kenneth Gonsalves
Senior Project Officer
NRC-FOSS
http://nrcfosshelpline.in/web/

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: A simple database project

2009-11-10T16:21:00Z

Hi Tomasz,

I was able to build the admin page and put a search box there:

class LawyerAdmin(admin.ModelAdmin):
fieldsets = [
('Name', {'fields': ['last', 'first', 'initial']}),
('School', {'fields': ['school', 'year_graduated']}),
]
list_display = ('first', 'initial', 'last', 'school',
'year_graduated')
list_filter = ['year_graduated']
search_fields = ['last', 'first']

This search box searches only first and last names. But what i want is
a search box that finds all lawyers who went to same school. My
database now contains:

Tom T. Lawyer3 Columbia School of Law 2003
Bob Lawyer2 NYU 2000
John I Lawyer1 NYU 2000

So Lawyer1 and Lawyer2 graduated from NYU in 2000.

So I want to enter in the search box "Lawyer1" and in the result page
I want to see "Lawyer1 knows Lawyer2"

How do I do this?

Thank you so much.

On Nov 7, 12:23 pm, Tomasz Zieliński
<tomasz.zielin...@...> wrote:

> On 7 Lis, 15:58, Zeynel <azeyn...@...> wrote:
>
> > Hello,
>
> > I am planning to build a demo prototype for a who-knows-who database
> > for the legal profession. Database will consist of lawyer name, school
> > and year graduated. Searching by lawyer name will return other lawyers
> > graduated from same law school the same year. Can I build this in
> > Django? How long would it take me to learn enough Django to build this
> > myself?
>
> Of course you can build this in Django, I think that going through
> tutorial:
>
> http://docs.djangoproject.com/en/dev/intro/tutorial01/
>
> is enough to build it in no longer that a few days (learning
> included),
> even for pre-intermediate programmer.
>
> --
> Tomasz Zielińskihttp://pyconsultant.eu

From forum: django-users

Re: How to handle this race condition?

2009-11-10T16:00:33Z

Ah, you're absolutely right. I am not sure how I didn't even catch the other thing that should have grabbed my attention this morning, which was that the table I was using was MyISAM. This is why I shouldn't send emails before noon :)

Sorry about that, that was my mistake.

Craig

On Tue, Nov 10, 2009 at 3:28 PM, akaariai <akaariai@...> wrote:

You missed the 'where bid < new_bid' part of the update. In that case
there is no race I am aware of. Either the transaction sees the update
of the other transaction in which case the highest bid will stay in
effect or it will not see the effect of the other transaction in which
case there is concurrent update and the transaction is aborted.

Anyways, as concurrency is hard and taking row level locks is cheap
and easy way to get the concurrency right I would suggest you use the
select for update method. Also, this way you will avoid the need to
retry failed transactions because of concurrent updates.

On Nov 10, 9:55 pm, Craig Kimerer <craig.kime...@...> wrote:

> On Mon, Nov 9, 2009 at 10:56 PM, Tamas Szabo <szab...@...> wrote:
> > Would something like
>
> > UPDATE bid = new_bid WHERE id = id and bid < new_bid
>
> > work for you?
>
> > It is a more optimistic approach (it assumes that the case you describe is
> > an exception rather than what usually happens) and I think it is simpler by
> > not having to do any locking etc.
>
> > Regards,
>
> > Tamas
>
> That only works if you have transactions disabled for your database. If
> your connections are using transactions, you still have the race condition.
>
> For example (in MySQL):
> Start two DB Shells
>
> In the first shell:
>
> mysql> insert into bids (id, high_bid) values (1, 20);
> Query OK, 1 row affected (0.00 sec)
>
> mysql> START TRANSACTION;
> Query OK, 0 rows affected (0.01 sec)
>
> In the second shell:
>
> mysql> START TRANSACTION;
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> update bids set high_bid = 25 where id = 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1 Changed: 1 Warnings: 0
>
> mysql> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> Back in the first shell:
>
> mysql> UPDATE bids SET high_bid = 23 where id = 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1 Changed: 1 Warnings: 0
>
> mysql> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> select * from bids;
> +------+----------+
> | id | high_bid |
> +------+----------+
> | 1 | 23 |
> +------+----------+
> 1 row in set (0.00 sec)
>
> Craig
>
>
>

> > On Tue, Nov 10, 2009 at 2:17 PM, Continuation <selforgani...@...>wrote:

>
> >> Thanks Christophe and Kenneth!
>
> >> Let me make sure I understand this:
>
> >> If I write this vew function:
>
> >> @transaction.commit_on_success
> >> def update_high_bid(request):
> >> ....
> >> cursor = connection.cursor()
> >> cursor.execute("SELECT high_bid FROM auctionapp_auction WHERE
> >> id=%s
> >> FOR UPDATE", [auction.id])
> >> returned_rows = cursor.fetchall()
> >> high_bid = returned_rows[0][0]
> >> if new_bid > high_bid:
> >> auction.high_bid = new_bid
> >> auction.save()
>
> >> The entire function will be wrapped within a transaction.
> >> SELECT FOR UPDATE will acquire a row-level lock
> >> and that lock will not be released until the function update_high_bid
> >> () returns successfully, or until the function raises an exception and
> >> the whole transaction is rolled back.
>
> >> Is that right?
>
> >> Thanks.
>
> >> On Nov 10, 12:45 am, Christophe Pettus <x...@...> wrote:
> >> > On Nov 9, 2009, at 9:34 PM, Continuation wrote:
>
> >> > > Also does django middleware acquire database lock on my behalf, or do
> >> > > I need to explicitly perform the locking?
>
> >> > In the example code, it's the SELECT ... FOR UPDATE that acquires the
> >> > lock. Django doesn't currently have any explicit knowledge of
> >> > locking, so you need to drop down to the custom SQL level to issue the
> >> > right statement to acquire the lock on the row.
>
> >> > The example I wrote assumed you were using PostgreSQL as the backend;
> >> > you can get all sorts of details about locking in PostgreSQL here:
>
> >>http://www.postgresql.org/docs/8.4/interactive/explicit-locking.html#...
> >> > --
> >> > -- Christophe Pettus
> >> > x...@...
>
>

From forum: django-users

Re: template or is it template_name

2009-11-10T15:53:57Z

On Wed, Nov 11, 2009 at 5:06 AM, Sean Brant <brant.sean@...> wrote:
>
> Stop me if you have heard this one before. Anyone else find it
> annoying that direct_to_template takes the kwarg "template" and most
> other generic views take "template_name". Smells a little like php to
> me.
>
> Is this something that should be / can be fixed?

Agreed that it is an annoying wart.

I can see two ways we can address this.

Firstly we can introduce a 'template_name' argument to
direct_to_template that shadows the existing 'template' argument. An
error would be raised if you specify both; using 'template' would
raise a Deprecation warning.

Secondly, we can ignore it in the current implementation, and use the
migration to class-based generic views (#6735) as an excuse to clean
up that bit of API.

Patches welcome :-)

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-developers

Re: [Django] #9286: Starting other processes in a view gives me some weird results.

2009-11-10T15:52:58Z

#9286: Starting other processes in a view gives me some weird results.
------------------------------------+---------------------------------------
Reporter: namename12 | Owner: nobody
Status: closed | Milestone: 1.1
Component: Uncategorized | Version: 1.0
Resolution: worksforme | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by Alex):

* status: reopened => closed
* resolution: => worksforme

Comment:

This bug was closed by a core developer, if you disagree please bring this
up for discussion ont he django-development mailiing list.

--
Ticket URL: <http://code.djangoproject.com/ticket/9286#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Happy 5th Brithday Firefox

2009-11-10T15:47:01Z

hmmm it seems we forgot to greet and thank Firefox for it's 5th year of existence!

http://www.spreadfirefox.com/5years/en-US/
http://zi.pe/eft

From forum: django-users

Re: Imports, works from directory but not from file

2009-11-10T15:46:32Z

Did you really mean "init.py", rather than the required "__init__.py".
If so, that's wrong.

I presume that the names of the files and directories are all lower
case and contain no spaces or accented characters.

I presume that you've checked and rechecked the spelling of the file
name against the spelling in the import statement.

It is just possible that it's a permission problem. Can you open the
files for reading? In the manage.py shell try (and assuming FILE_ROOT
is the current directory):

open('lib/openid/association.py').readline()

If that doesn't give an exception, but just prints the first line of
the file, good.

If there's an association.pyc remove it and try again (write
permission problem to replace file
with compiled python for the version of the interpreter in use, though
I think it would work fine
anyway).

I'd expect a different exception, but maybe a problem in
association.py is preventing it from importing. Try adding:

import pdb;pdb.set_trace()

to the top of association.py and see if it gets there and stops, then
step along ("n" command) to see that it all completes.

Check that the file doesn't have Apple line endings ('\r' only). I
know that both DOS and *nix line endings work on Windows ('\r\n' and
'\n' respectively).

There could be problems if the file is in a unicode variant as opposed
to simple 7 bit ASCII, though I hope not. That would probably be
clear from the open test above.

Check that the __init__.py files are either empty, or have valid
python contents.

Beyond that, I'm out of ideas. Good luck.

Bill

On Tue, Nov 10, 2009 at 5:24 PM, When ideas fail
<andrewkenyon123@...> wrote:

>
> I used this in my settings.py to add the open id folder on my path
> sys.path.append(os.path.join(FILE_ROOT, 'lib', 'openid'))
>
> and on my path it say:
> 'C:\\TheAbeonaFile\\Python26\\Lib\\idlelib\\lib\\openid'
>
> And both the yadis file and openid file have an init.py
>
> On 10 Nov, 22:18, Bill Freeman <ke1g...@...> wrote:
>> Which all of these directories are on your python path, and which of
>> them have __init__.py files?
>>
>> Bill
>>
>> [Hint to answer first question:
>>
>> from pprint import pprint as pp
>> import sys
>> pp(sys.path)
>>
>> ]
>>
>> On Tue, Nov 10, 2009 at 5:12 PM, When ideas fail
>>
>> <andrewkenyon...@...> wrote:
>>
>> > I have a folder called lib on my path and in there I have a folder
>> > called openid.
>>
>> > If i want to import things from openid i have a problem.
>>
>> > For example if I have these 2 import statements:
>>
>> > from openid.yadis import xri
>> > from openid.association import Association as OIDAssociation
>>
>> > yadis is a directory (in openid) and then there is xri.py inside. This
>> > works fine.
>> > association is a .py file not in a subdirectory, just in lib/openid
>> > this produces the following error:
>>
>> > Traceback (most recent call last):
>> > File "C:\TheAbeonaFile\Apache2.2\MyProject\test.py", line 18, in
>> > <module>
>> > from openid.association import Association as OIDAssociation
>> > ImportError: No module named association
>>
>> > I don't see why one would be a problem and not the other, does anyone
>> > have any ideas?
>>
>> > thanks
> >
>

From forum: django-users

Happy 5th Brithday Firefox

2009-11-10T15:44:52Z

hmmm it seems we forgot to greet and thank Firefox for it's 5th year of existence!

http://www.spreadfirefox.com/5years/en-US/
http://zi.pe/eft

From forum: django-users

Re: Model field validation for admin

2009-11-10T15:44:33Z

> > > Hello, I want to make a field optional (blank=True), only if another
> > > text field's options match a certain value in the admin. Is there any
> > > way to do this? Thanks!

You want to do this in a modelform, and then specify that model form
in your admin.py. Put the checks in the overall form clean method (as
it refers to more than one field). In your model allow blank/null.

Peter
--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

datetime problems with Django application

2009-11-10T15:41:01Z

I have a Django application running with mod_python on Apache. In
settings.py I have set TIME_ZONE="America/New_York". Within my
application I verify that os.environ['TZ'] is indeed set to this
value. Within my view.py I use datetime.datetime.now() to create a
time stamp that is stored in a model as a DateTimeField and viewed on
a rendered html page.

However, the times that I generate in my view are all off from what
they should be by five hours. I've changed the time zone around
"America/Chicago", "America/Anchorage" etc. no matter what I set
TIME_ZONE to, I get the same wrong time (5 hours off).

If I go to the admin page and use the change entry page to modify the
values stored in the database, the Time now link gives the correct
time?

Any idea on what is going on here? I'm particularly perplexed as to
why the admin page and my view are giving different times.

Brian

--~--~---------~--~----~------------~-------~--~----~
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@...
To unsubscribe from this group, send email to django-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-users

Re: [Django] #9286: Starting other processes in a view gives me some weird results.

2009-11-10T15:32:40Z

#9286: Starting other processes in a view gives me some weird results.
------------------------------------+---------------------------------------
Reporter: namename12 | Owner: nobody
Status: reopened | Milestone: 1.1
Component: Uncategorized | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by stevecrozz@...):

* status: closed => reopened
* resolution: worksforme =>

Comment:

I'd call this a bug, and its affecting me.

The django development server is able to start a background process, but
for some reason it must block until the sub process dies. Place something
like this in a view and you'll get your response 5 seconds later,
Popen.communicate() is not needed to reproduce it:

{{{
subprocess.Popen(['/bin/sleep', '5'])
return HttpResponse(u'That sure took a while!')
}}}

Also see #4953 and #3712

--
Ticket URL: <http://code.djangoproject.com/ticket/9286#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates

Re: How to handle this race condition?

2009-11-10T15:28:26Z

You missed the 'where bid < new_bid' part of the update. In that case
there is no race I am aware of. Either the transaction sees the update
of the other transaction in which case the highest bid will stay in
effect or it will not see the effect of the other transaction in which
case there is concurrent update and the transaction is aborted.

Anyways, as concurrency is hard and taking row level locks is cheap
and easy way to get the concurrency right I would suggest you use the
select for update method. Also, this way you will avoid the need to
retry failed transactions because of concurrent updates.

On Nov 10, 9:55 pm, Craig Kimerer <craig.kime...@...> wrote:

> On Mon, Nov 9, 2009 at 10:56 PM, Tamas Szabo <szab...@...> wrote:
> > Would something like
>
> > UPDATE bid = new_bid WHERE id = id and bid < new_bid
>
> > work for you?
>
> > It is a more optimistic approach (it assumes that the case you describe is
> > an exception rather than what usually happens) and I think it is simpler by
> > not having to do any locking etc.
>
> > Regards,
>
> > Tamas
>
> That only works if you have transactions disabled for your database. If
> your connections are using transactions, you still have the race condition.
>
> For example (in MySQL):
> Start two DB Shells
>
> In the first shell:
>
> mysql> insert into bids (id, high_bid) values (1, 20);
> Query OK, 1 row affected (0.00 sec)
>
> mysql> START TRANSACTION;
> Query OK, 0 rows affected (0.01 sec)
>
> In the second shell:
>
> mysql> START TRANSACTION;
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> update bids set high_bid = 25 where id = 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1 Changed: 1 Warnings: 0
>
> mysql> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> Back in the first shell:
>
> mysql> UPDATE bids SET high_bid = 23 where id = 1;
> Query OK, 1 row affected (0.00 sec)
> Rows matched: 1 Changed: 1 Warnings: 0
>
> mysql> commit;
> Query OK, 0 rows affected (0.00 sec)
>
> mysql> select * from bids;
> +------+----------+
> | id | high_bid |
> +------+----------+
> | 1 | 23 |
> +------+----------+
> 1 row in set (0.00 sec)
>
> Craig
>
>
>
> > On Tue, Nov 10, 2009 at 2:17 PM, Continuation <selforgani...@...>wrote:
>
> >> Thanks Christophe and Kenneth!
>
> >> Let me make sure I understand this:
>
> >> If I write this vew function:
>
> >> @transaction.commit_on_success
> >> def update_high_bid(request):
> >> ....
> >> cursor = connection.cursor()
> >> cursor.execute("SELECT high_bid FROM auctionapp_auction WHERE
> >> id=%s
> >> FOR UPDATE", [auction.id])
> >> returned_rows = cursor.fetchall()
> >> high_bid = returned_rows[0][0]
> >> if new_bid > high_bid:
> >> auction.high_bid = new_bid
> >> auction.save()
>
> >> The entire function will be wrapped within a transaction.
> >> SELECT FOR UPDATE will acquire a row-level lock
> >> and that lock will not be released until the function update_high_bid
> >> () returns successfully, or until the function raises an exception and
> >> the whole transaction is rolled back.
>
> >> Is that right?
>
> >> Thanks.
>
> >> On Nov 10, 12:45 am, Christophe Pettus <x...@...> wrote:
> >> > On Nov 9, 2009, at 9:34 PM, Continuation wrote:
>
> >> > > Also does django middleware acquire database lock on my behalf, or do
> >> > > I need to explicitly perform the locking?
>
> >> > In the example code, it's the SELECT ... FOR UPDATE that acquires the
> >> > lock. Django doesn't currently have any explicit knowledge of
> >> > locking, so you need to drop down to the custom SQL level to issue the
> >> > right statement to acquire the lock on the row.
>
> >> > The example I wrote assumed you were using PostgreSQL as the backend;
> >> > you can get all sorts of details about locking in PostgreSQL here:
>
> >>http://www.postgresql.org/docs/8.4/interactive/explicit-locking.html#...
> >> > --
> >> > -- Christophe Pettus
> >> > x...@...
>
>

From forum: django-users

Re: [Django] #12196: EmailField reject this email address tosha...99@gmail.com

2009-11-10T15:17:50Z

#12196: EmailField reject this email address tosha...99@...
---------------------------------+------------------------------------------
Reporter: mtsyganov | Owner: nobody
Status: new | Milestone:
Component: Forms | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------+------------------------------------------
Changes (by Alex):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0

Old description:

> To fix that problem, just change
>
> email_re = re.compile(
> r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]+)*" #
> dot-atom
> r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
> # quoted-string
> r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$',
> re.IGNORECASE) # domain
>
> TO
>
> email_re = re.compile(
> r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]*)*" #
> dot-atom
> r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
> # quoted-string
> r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$',
> re.IGNORECASE) # domain
>
> in the file django.forms.fields.py
>
> I just replaced in the first line the + to *

New description:

To fix that problem, just change
{{{
email_re = re.compile(
r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]+)*" #
dot-atom
r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
# quoted-string
r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$',
re.IGNORECASE) # domain
}}}
TO
{{{
email_re = re.compile(
r"(^[-!#$%&'*+/=?^_`{}|~0-9A-Z]+(\.[-!#$%&'*+/=?^_`{}|~0-9A-Z]*)*" #
dot-atom
r'|^"([\001-\010\013\014\016-\037!#-\[\]-\177]|\\[\001-011\013\014\016-\177])*"'
# quoted-string
r')@(?:[A-Z0-9](?:[A-Z0-9-]{0,61}[A-Z0-9])?\.)+[A-Z]{2,6}\.?$',
re.IGNORECASE) # domain
}}}
in the file django.forms.fields.py

I just replaced in the first line the + to *

Comment:

Please use preview.

--
Ticket URL: <http://code.djangoproject.com/ticket/12196#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django updates" group.
To post to this group, send email to django-updates@...
To unsubscribe from this group, send email to django-updates+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

From forum: django-updates