I've just spent a few hours fiddling with the patch to adapt it to
PostgreSQL, and
the final result was that I have managed to get what field was producing
the error.
Then I rolled evolution back, commented that field, applied the changes,
uncommented
the field and applied the changes back.
My opinion is that it would be great if we could just get a sensible error
message
from Evolution, with clear indication of the field which creates the
problem; it can
then easily be solved in other ways.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings