2007/1/19, Dave Page <dpage@postgresql.org>:
> Clodoaldo wrote:
> > 2007/1/18, Dave Page <dpage@postgresql.org>:
> >>
> >>
> >> > ------- Original Message -------
> >> > From: Laurent ROCHE <laurent_roche@yahoo.com>
> >> > To: pgadmin-support@postgresql.org
> >> > Sent: 1/18/07, 7:21:35 PM
> >> > Subject: [pgadmin-support] Crash and sending report !
> >> >
> >> > Hi,
> >> >
> >> > When ever there's a crash (it's about every other time ... when I
> >> close PG Admin ... so no big deal ;-) !) is it worth me sending the
> >> report to Microsoft ?
> >> > Does it get to the PG Admin people in the end ?
> >> >
> >>
> >> LOL! No, we'll never see those!
> >>
> >> What crashes though? That should never happen :-(
> >
> > I can always reproduce a crash:
> >
> > 1) Right click a table
> > 2) Select View Data -> View top 100 rows
> > 3) Click the row number to select it
> > 4) Click the delete icon (Trash)
> > 5) Click Yes on the confirmation dialog.
> > 6) Certain crash
> >
> > The row is not deleted. I can delete it with a delete command in psql.
> >
>
> Works fine for me with my dummy data - but I did have to remove the
> foreign key and the call to valida_cpf(cpf) in the cpf check constraint.
>
> When you delete in psql, do you see any notices from the backend?
No
> Are
> there any other tables referencing this one that might be preventing the
> delete (not that that should cause a crash either of course).
Yes, there is a table with a FK referencing this one. But I'm deleting
a not referenced row to reproduce the crash.
I also tried to delete a row referenced by that other table and it
crashs the same.
If there is a method to trace the crash just let me know and I will
try to use it.
Regards,
--
Clodoaldo Pinto Neto
