Thanks
> It looks like there was some XML issues. Murray, what do you think of
those errors.
I guess you mean this:
STATEMENT: SELECT "glom_system_autoincrements"."next_value" FROM
"glom_system_autoincrements" WHERE "table_name" = '83test' AND
"field_name" = '83test_id'
(glom:6174): glibmm-CRITICAL **:
unhandled exception (type Glib::Error) in signal handler:
domain: gda_connection_error
code : 6
what : ERROR: operator does not exist: xml = unknown
LINE 1: ...M "glom_system_autoincrements" WHERE "table_name" = '83test'...
^
HINT: No operator matches the given name and argument type(s). You might need
to add explicit type casts.
I haven't seen that before and I don't understand it yet, but I will switch to
Postgres 8.3 and investigate. Did this only happen with glom 1.6.8? Or was
there another reason that you only packaged 1.6.6 again?
If you could get the latest libgda 3.0.x and libgdamm versions in
Ubuntu then that would make the picture clearer.
--
Glom should depend on postgresql-8.3
https://bugs.launchpad.net/bugs/188939
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
