Re: weird auto-increment problem
- From: Murray Cumming <murrayc murrayc com>
- To: Ryan Paul <ryankpaul gmail com>
- Cc: glom-devel-list gnome org
- Subject: Re: weird auto-increment problem
- Date: Sat, 28 Oct 2006 13:03:00 +0200
On Sat, 2006-10-28 at 02:06 -0700, Ryan Paul wrote:
On Sat, 2006-10-28 at 10:41 +0200, Murray Cumming wrote:
What version of Glom is this?
Glom 1.0.3, Posgres 7.4 (running on Ubuntu Dapper)
A lot of bugs have been fixed since then. I do wish that Ubuntu Dapper
would update its version to the latest 1.0.x version (1.0.8).
Ubuntu Edgy has Glom 1.2.0, if you are ready to upgrade your entire
system. Otherwise you might try building from source to see whether the
problem is fixed.
Do you seen any interesting debug output when you run it from a terminal?
No, nothing out of the ordinary, just the usual GTK stuff:
(:26873): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion
`node != NULL' failed
(:26873): Gtk-CRITICAL **: gtk_widget_event: assertion
`WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
(:26873): Gtk-CRITICAL **: gtk_widget_event: assertion
`WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
Is it possible that you have changed the database structure somehow
without using Glom to do that?
I don't think so. The only operations that I have performed outside of
Glom are simple inserts, updates, and selects on existing tables.
Is this a bug that nobody has encountered before? I'll try to make some
time later today to create another Glom database and see if it exhibits
the same problems. I'll let you know what happens. Anything else I
should try?
Thanks. You might also try sending me your .glom file, so I can see
whether there is anything wrong with that, with the latest version.
It would be most convenient if we can do this investigation in bugzilla.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]