GDA: empty PostgreSQL table failed workaround

Previously, I had suggested a workaround for the empty PostgreSQL slots table problem. I have now tried the work-around for the empty slots table problem with PostgreSQL. The type SERIAL is simply a convenience, and not a real type. I had hoped the convenience extended to ALTER TABLE, but it

Re: GDA: empty PostgreSQL table failed workaround

Mark Johnson wrote: > Previously, I had suggested a workaround for the empty PostgreSQL slots > table problem. > > I have now tried the work-around for the empty slots table problem with > PostgreSQL. The type SERIAL is simply a convenience, and not a real > type. I had hoped the convenience e

Re: www.gnucash.org down?

Hi, Please remember to keep this on the list. I've cc'd it back to gnucash-devel. Please remember to Reply-To-List or Reply-All when replying. Thilo Pfennig <[EMAIL PROTECTED]> writes: > Am Sun, 10 Feb 2008 09:11:05 -0500 > schrieb Derek Atkins <[EMAIL PROTECTED]>: > >> If you DO configure a m

Re: GDA: empty PostgreSQL table failed workaround

Hi, Phil Longstaff <[EMAIL PROTECTED]> writes: > Saving to the db deletes all tables and then recreates them. It > therefore deleted the slot_id without the default value. It wouldn't > have touched the sequence. I'll need to build your workaround into a > rev and then let you try it. Ther

Re: GDA: empty PostgreSQL table failed workaround

Derek Atkins wrote: > Hi, > > Phil Longstaff <[EMAIL PROTECTED]> writes: > > >> Saving to the db deletes all tables and then recreates them. It >> therefore deleted the slot_id without the default value. It wouldn't >> have touched the sequence. I'll need to build your workaround into a >>

Re: GDA: empty PostgreSQL table failed workaround

Saving to the db deletes all tables and then recreates them. It therefore deleted the slot_id without the default value. It wouldn't have touched the sequence. I'll need to build your workaround into a rev and then let you try it. There's also an argument to be made that I should

Re: GDA: empty PostgreSQL table failed workaround

Quoting Greg Troxel <[EMAIL PROTECTED]>: > Saving to the db deletes all tables and then recreates them. It > therefore deleted the slot_id without the default value. It wouldn't > have touched the sequence. I'll need to build your workaround into a > rev and then let you try it. There's al

Re: GDA: empty PostgreSQL table failed workaround

Phil Longstaff wrote: > The slot_id is used to provide a unique primary key. I don't know if it > would work to have the slots table have *no* key, but have an index on > the obj_guid field. The obj_guid field can't be the primary key because > I believe a primary key needs to be unique. Mark

Re: GDA: empty PostgreSQL table failed workaround

Phil Longstaff wrote: > Mark Johnson wrote: > >> Previously, I had suggested a workaround for the empty PostgreSQL slots >> table problem. >> >> I have now tried the work-around for the empty slots table problem with >> PostgreSQL. The type SERIAL is simply a convenience, and not a real >> t

QIF importer patches

Any chance of committing a few more patches to the QIF importer before 2.2.4? In particular, the patch for bug 513829fixes a pretty blatant error in the import results and is affecting a user trying to migrate to GnuCash. And its a two-fer... this o

Re: GDA: empty PostgreSQL table failed workaround

2008/2/13, Mark Johnson <[EMAIL PROTECTED]>: > Phil Longstaff wrote: > > The slot_id is used to provide a unique primary key. I don't know if it > > would work to have the slots table have *no* key, but have an index on > > the obj_guid field. The obj_guid field can't be the primary key because >

Re: GDA: empty PostgreSQL table failed workaround

Quoting Daniel Espinosa <[EMAIL PROTECTED]>: > 2008/2/13, Mark Johnson <[EMAIL PROTECTED]>: >> Phil Longstaff wrote: >> > The slot_id is used to provide a unique primary key. I don't know if it >> > would work to have the slots table have *no* key, but have an index on >> > the obj_guid field. T

Re: gda crash in load_owner() with PostgreSQL backend

Graham Menhennitt wrote: > G'day all, > > I've successfully built the gda branch version 16939 from SVN. I can run > it with a normal gnucash data file as the command line parameter and > then save to a PostgreSQL DSN using the File->Database Connection menu > item. By looking in the DB using psql,

Re: Glade urgency_hint property

Are the last_modification_time attributes a problem? I noticed there is one currently in qif.glade already but I'm not sure about any potential problems. Also, BTW, I noticed that after running util/glade-fixup that src/gnome-utils/glade/dialog-book-close.glade was modified to remove an urgency_hi