Re: Add row broken still

2003-07-22 Thread Andre Poenitz
On Tue, Jul 22, 2003 at 09:39:35AM +0100, Jose' Matos wrote: > On Tuesday 22 July 2003 09:32, Andre Poenitz wrote: > > > > ETA? > > Estimated time arrival (IIRC). "Christmas". Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either

Re: Add row broken still

2003-07-22 Thread Jose' Matos
On Tuesday 22 July 2003 09:32, Andre Poenitz wrote: > > ETA? Estimated time arrival (IIRC). > Andre' -- José Abílio

Re: Add row broken still

2003-07-22 Thread Andre Poenitz
On Tue, Jul 22, 2003 at 02:00:02AM -0300, Garst R. Reese wrote: > Andre Poenitz wrote: > > > It's my fault... > I guessed that from the ChangeLogs :) > Do you have an ETA for a fix? ETA? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserv

Re: Add row broken still

2003-07-21 Thread Garst R. Reese
Andre Poenitz wrote: > It's my fault... I guessed that from the ChangeLogs :) Do you have an ETA for a fix? anyway, KUTGW Garst text not available! no text in cache! InsetTabular::updateLocal: 0 create: first_id orig: 5 create: last_id orig:5 create: first_id: 5 create: last_id:

Re: Add row broken still

2003-07-21 Thread Andre Poenitz
On Sat, Jul 19, 2003 at 12:15:35AM -0300, Garst R. Reese wrote: > Just a reminder that adding a row to a table crashes 1.4CVS > As reported earlier, CPU usage goes toward 100% then crash. > Breakeage happened sometime after June 30. It's my fault... Andre' -- Those who desire to give up Freedom

Re: Add row broken still

2003-07-21 Thread Andre Poenitz
On Sat, Jul 19, 2003 at 12:15:35AM -0300, Garst R. Reese wrote: > Just a reminder that adding a row to a table crashes 1.4CVS > As reported earlier, CPU usage goes toward 100% then crash. > Breakeage happened sometime after June 30. It's my fault... Andre' -- Those who desire to give up Freedom

Add row broken still

2003-07-20 Thread Garst R. Reese
Just a reminder that adding a row to a table crashes 1.4CVS As reported earlier, CPU usage goes toward 100% then crash. Breakeage happened sometime after June 30. xforms-1.0.2 Garst