Hi, Are you creating Dlist's within a transaction and then not persisting them? I ran into this issue amd didn't really find a satisfactory answer... I would really like to use a general list class (with ordering!) that can be made persistent but doesn't need the overhead/space of re-storing every entry in the DLIST tables... Let alone entries/lists that were never persisted!
Maybe someone else has some new ideas Rob :) > -----Original Message----- > From: Gunnar Hilling [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 7 January 2004 9:06 p.m. > To: [EMAIL PROTECTED] > Subject: ojb_dlist_entries continues to grow ... > > > Hello all, > > Is it normal, that the ojb_dlist_entries table grows on and > on? Or ist this just caused by rollbacked transactions? > > I think I'll have soon problems because my database becomes > quite large just by ojb_dlist_entries... > > Any clue? > > -Gunnar > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
