Spelling errors in database error description

[Frank tegtmeyer <fte@…>]

There is a spelling error and a somewhat ugly wording in the error message about a mismatching database.
Patch provided.

--- django/conf/locale/de/LC_MESSAGES/django.po.original        Thu May 24 12:25:14 2007
+++ django/conf/locale/de/LC_MESSAGES/django.po Thu May 24 12:27:33 2007
@@ -481,8 +481,8 @@
 "database tables have been created, and make sure the database is readable by "
 "the appropriate user."
 msgstr ""
-"Etwas stimmt nicht mit der Datenbankkonfiguration. Bitte sicherstellen, das "
-"die richtigen Datenbanktabellen angelegt wurden und bitte sicherstellen, das "
+"Etwas stimmt nicht mit der Datenbankkonfiguration. Bitte sicherstellen, dass "
+"die richtigen Datenbanktabellen angelegt wurden und "
 "die Datenbank vom verwendeten Datenbankbenutzer auch lesbar ist."
 
 #: contrib/admin/templates/admin/login.html:17

[fte@…]

patch for german translation

[Marc Fargas <telenieko@…>]

Don't speak german, but the correction seems ok, at least the first line is ok unless german people like double to 's' :)

[Malcolm Tredinnick]

(In [5350]) Fixed #4377 -- Small tweak to the German translation. Thanks, Frank Tegtmeyer.

[Praveen]

def queryset(self, request):
        	qs = super(EventAdmin, self).queryset(request)
        	if not request.user.is_superuser:
            		qs = qs.filter(city=request.user.get_profile().res_city)
        	return qs

it works fine as but it list out all the city's events

def queryset(self, request):
        	qs = super(EventAdmin, self).queryset(request)
        	if request.user.is_superuser:
            		qs = qs.filter(city=request.user.get_profile().res_city)
        	return qs

but when i change the if condition it gives error message

Database error

Something's wrong with your database installation. Make sure the appropriate database tables have been created, and make sure the database is readable by the appropriate user.

[Ramiro Morales]

You've done two things wrong:

• Reopening a ticket that has been closed because it was fixed but without having seen the same error condition reported originally.
• Re-purposing a ticket to something totally different (translations -> authentication) just because they happen to have the same literal in the summary field. Doing this you broke the history of this ticket for people looking for the issue associated with it and its corresponding fix.

The effort this took you is the same effort it would take to send an e-mail to django-users (preferred) or to open another ticket.

[Praveen]

Sorry this was my first time so did not know how to post ticket and this ticket was resemblance to my problem

[Jacob]

Milestone 1.0.3 deleted