[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] login problem / beginner
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] login problem / beginner |
Date: |
Fri, 6 Feb 2009 15:02:49 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
This issue:
> 2008-12-01 23:48:14 ERROR gm.person
> (/var/lib/python-support/python2.5/Gnumed/business/gmPerson.py::__init__()
> #762): cannot instantiate staff instance
> Traceback (most recent call last):
> File "/var/lib/python-support/python2.5/Gnumed/business/gmPerson.py", line
> 760, in __init__
> rows, idx = gmPG2.run_ro_queries(queries = [{'cmd': cmd}], get_col_idx=True,
> verbose=True)
> File "/var/lib/python-support/python2.5/Gnumed/pycommon/gmPG2.py", line 815,
> in run_ro_queries
> data = curs.fetchall()
> File "/usr/lib/python2.5/site-packages/psycopg2/extras.py", line 60, in
> fetchall
> return _cursor.fetchall(self)
> DataError: unable to parse time
has now been observed on both
> Ubuntu Intrepid
(recent report)
and
> My system: Linux 2.6.24-2.6.24.4.slh.5-sidux-amd64 #1 SMP PREEMPT Fri Apr 11
> 21:52:15 UTC 2008 x86_64 GNU/Linux
(somewhat older report from Peter Hechler)
It is some sort of interaction BELOW GNUmed with the known
or suspected properties:
- psycopg 2.0.8
- 64 bit machine (?)
- PostgreSQL 8.3
- client 0.3.8 and 0.3.9
This problem does NOT occur on Debian/Testing 32 bit with PG
8.3 and psycopg2.0.8 and client 0.3.x or 0.4.
So, in conclusion, we need more information and someone
willing to help with debugging.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Gnumed-devel] login problem / beginner,
Karsten Hilbert <=