On Feb 12, 6:40 am, paul <phart...@gmail.com> wrote: > hello -- just let me know if my description below sounds like a bug. > If so, I can try to put together a decent bug report... > > I am working on fleshing out the integration of a custom > authentication backend. Basically I have a OpenLDAP directory that is > used to store user names and passwords (in conjunction with Samba -- > entries are inputted using smbldap-tools). I have the backend working > just fine -- I can get a login screen, enter an appropriate username > and password, and can confirm that the password is being authenticated > correctly through a comparison with the password stored in the LDAP > server. > > Now the weird part... the next step after logging in is obviously to > redirect to another HTML page. I was originally using PostgreSQL > (8.4, via psycopg2) while coding, and was never able to get redirected > to a new page and instead got a traceback (see below) printed to my > WWW browser. I decided to try switching to MySQL (5.0), and did not > replicate this issue -- while running MySQL I'm redirected to a web > page after logging in.
MySQL's default storage engine (MyISAM) doesn't support transactions, so no wonder you don't have a pending transaction. Perhaps you'll find some answer here: http://docs.djangoproject.com/en/1.1/topics/db/transactions/#handling-exceptions-within-postgresql-transactions HTH -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
