23 Nov
2012
23 Nov
'12
14:35
On Fri, 23 Nov 2012 13:37:11 +0100 Matej Gregr igregr@fit.vutbr.cz wrote:
However: nav ~> nav version NAV 3.12.2
and the DB scheme is still the same (old with the error), so the fix was not applied. Strange.
Can you verify the schema using NAV's syncdb.py?
--
Morten Brekkevold
UNINETT