RT 2.1.4 Recursive group membership

So, the big change in 2.1.4 is that Groups can now contain other groups as members. Other changes:

The web and command line interfaces support this new functionality

The FastCGI interface is closer to working. We need a change to
HTML::Mason to make it work anywhere but on my laptop. More to 
come on that one.

RT now uses innodb tables on mysql. They're faster and they support...

Transactions. That's right, transactions.  Starting with the new
group membership code, sections of RT's core will be transactionalized.
(Because of this, this code _needs_ the latest DBIx::SearchBuilder,
which will be release soon)

As yet, the postgres schema is still out of sync. It will likely
lag a bit as the schema stabilizes.

Don't run this release, unless you really _want_ jackals to
claw out your eyes.


-j

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

“JV” == Jesse Vincent jesse@bestpractical.com writes:

JV> RT now uses innodb tables on mysql. They’re faster and they support…

JV> Transactions. That’s right, transactions. Starting with the new
JV> group membership code, sections of RT’s core will be transactionalized.

Do they do relational integrity (ie, foreign keys with cascaded
deletes/updates?) That would make cleanup of spam easier, since you
just need to delete the main ticket record and all associated records
would go away with it.

Do they do relational integrity (ie, foreign keys with cascaded
deletes/updates?) That would make cleanup of spam easier, since you
just need to delete the main ticket record and all associated records
would go away with it.

Sadly, mysql’s InnoDB table type doesn’t yet do cascaded deletes.
Once it does, my life will be much better, and I can yank out a whole
bunch of nasty code. :wink:
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.