Rt-users digest, Vol 1 #1169 - 8 msgs

Assume you mean marked “dead” and for RT2.

Someone here posted a script to do that a while back. What I did was
add referential constraints to the database with cascading deletes,
and then I do this: delete from tickets where status=‘dead’

I posted the constraints here last week. They don’t work for mysql
with the default setup for RT2.

I thought mysql didn’t support cascading delete/updates since it doesn’t
support foreign keys?
Nicolae P. Costescu, Ph.D. / Senior Developer
Stronghold Technologies
46040 Center Oak Plaza, Suite 160 / Sterling, Va 20166
Tel: 571-434-1472 / Fax: 571-434-1478

“NPC” == Nicolae P Costescu nick@strongholdtech.com writes:

I posted the constraints here last week. They don’t work for mysql
with the default setup for RT2.

NPC> I thought mysql didn’t support cascading delete/updates since it doesn’t
NPC> support foreign keys?

MySQL 4 with InnoDB tables does support referential constraints and
even transactions. They claim row-level locking too, but I haven’t
investigated how to make that work. I’m sticking with Postgres since
I already know it.

Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/