In data lunedì 16 dicembre 2013 09:56:55, Ferran Jorba ha scritto:
> > In this way we're going to have the whole stack trace with all the
> > offending values.
> 
> So you keep me busy for a while...  Good trick! ;-)

No seriosuly: that would really give all and every local value in the stack 
trace so we would be able to see for real in a consistent way which variable 
is the culprit, if any... It's a desperate maneuver given that your DB conf 
looks good, at first and second, and third look :-P

Cheers!
        Sam
-- 
Samuele Kaplun
Invenio Developer ** <http://invenio-software.org/>
INSPIRE Service Manager ** <http://inspirehep.net/>
Interim SCOAP3 Repository Manager ** <http://scoap3repo.cern.ch/>

Reply via email to