After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683162 - metastore update fails for table
metastore update fails for table
Status: RESOLVED FIXED
Product: libgda
Classification: Other
Component: Client library
5.1.x
Other Linux
: Normal normal
: ---
Assigned To: malerba
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-01 15:29 UTC by Murray Cumming
Modified: 2012-09-02 18:13 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gda_meta_update_tables.c (3.49 KB, text/x-csrc)
2012-09-01 15:29 UTC, Murray Cumming 		Details

Description Murray Cumming 2012-09-01 15:29:19 UTC 
Created attachment 223147 [details]
gda_meta_update_tables.c

With master, but not with the LIBGDA_5_0 branch, this test case emits this warning, though not a GError:

** (process:6645): WARNING **: Column 4 out of range (0-3), ignoring its specified type

After some git bisecting, I think this started with this commit:
http://git.gnome.org/browse/libgda/commit/?id=dacaa9e33b62c5ba2118e2b248a5ab4c56bf49a6

Here is the backtrace at that warning:

+ Trace 230776

  • #0 g_log
  • #1 finish_prep_stmt_init
    at gda-postgres-recordset.c line 295
  • #2 gda_postgres_recordset_new_random
    at gda-postgres-recordset.c line 342
  • #3 gda_postgres_provider_statement_execute
    at gda-postgres-provider.c line 2201
  • #4 gda_connection_statement_execute_select_full
    at gda-connection.c line 3978
  • #5 _gda_postgres_meta_schemata
    at gda-postgres-meta.c line 893
  • #6 local_meta_update
    at gda-connection.c line 4969
  • #7 suggest_update_cb_downstream
    at gda-connection.c line 5262
  • #8 _gda_marshal_ERROR__METACONTEXT
    at gda-custom-marshal.c line 330
  • #9 g_closure_invoke
    at gclosure.c line 777
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #11 g_signal_emit_valist
  • #12 g_signal_emit
    at gsignal.c line 3356
  • #13 gda_meta_store_modify_v
    at gda-meta-store.c line 3345
  • #14 gda_meta_store_modify
    at gda-meta-store.c line 2995
  • #15 _gda_postgres_meta__info
    at gda-postgres-meta.c line 341
  • #16 local_meta_update
    at gda-connection.c line 4782
  • #17 gda_connection_update_meta_store
    at gda-connection.c line 5405
  • #18 update_meta_store_for_table
  • #19 main 



I noticed this in Glom's test_selfhosting_new_then_change_columns regression test which then goes on to have a GError:

SUGGEST META UPDATE Returned FALSE: Data models should have the same number of columns
Comment 1 malerba 2012-09-01 19:46:25 UTC 
Can you check with commit http://git.gnome.org/browse/libgda/commit/?id=ad93194f0bef89f32760792aa74718c0e5c4c45b
Thanks!
Comment 2 Murray Cumming 2012-09-02 18:12:52 UTC 
Yes, all the warnings and the GError are gone now, both in that test case and in the Glom regression test. Many thanks.