Ubuntu
glom package

  1. Bug #188939
  2. Comment #13

Comment 13 for bug 188939

Revision history for this message
Murray Cumming (murrayc) wrote :

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.