On Apr 15, 9:53 pm, Jacob Kaplan-Moss <
jacob.kaplanm...@gmail.com>
wrote:
> On Wed, Apr 15, 2009 at 7:48 PM, Horacio de Oro <
hgde...@gmail.com> wrote:
>
> > Is this a bug? Should I file a bug report?
>
> Yes, please do. Thanks!
>
> Jacob
Testing with another applicatoin, I've found that
"request.user.is_authenticated()" produces the same exception on the
development web server (with Django 1.0.2).
Anyway, I've checked out the code from the git repository and and I've
found duplicated the code that get the postgrsql version in:
django/db/backends/postgresql/version.py (Django 1.1-dev)
VERSION_RE = re.compile(r'\S+ (\d+)\.(\d+)')
and:
django/db/backends/postgresql/operations.py (Django 1.1-dev)
server_version_re = re.compile(r'PostgreSQL (\d{1,2})\.(\d{1,2})\.?(\d
{1,2})?')
I've found some bug reports related to this (#6433, #8737, #9953), and
the the ticket #8737 says:
"PostgreSQL version detection is fragile; no longer works for
EnterpriseDB"
I think that it should be re-opened and at least change
server_version_re = re.compile(r'PostgreSQL (\d{1,2})\.(\d{1,2})\.?(\d
{1,2})?')
with:
server_version_re = re.compile(r'\S+ (\d{1,2})\.(\d{1,2})\.?(\d
{1,2})?')
This way, EnterpriseDB should works fine (this should be changed in
1.0.2 and 1.1-dev).
Maybe #6433 ("postgres backend doesn't accept version number 8.3RC2")
should be reopened, and apply this fixes on Django 1.0.2:
- In django/db/backends/postgresql/version.py, change
VERSION_RE = re.compile(r'PostgreSQL (\d+)\.(\d+)\.')
with the RE of current trunk:
VERSION_RE = re.compile(r'\S+ (\d+)\.(\d+)')
If you agree, I'd be glad to re-open those thickets, upload the
patches or both things.
Horacio