Hi Jason,
Jason Dixon wrote:
We also was thing about a reference table for ticket free text attributes. The only reason because we implemented ticket free text attributes this way is because of the performance of complex searches and a lot of ticket (> 1.000.000).
We tried different ways and the current one was the way with the best performance (of course a reference table whould be elegant way).
Which brings up the problem with a lack of foreign key support in MySQL's MyISAM tables. I'm not sure if this is in the works for MySQL 5.0, but it's available in the InnoDB table format as well as PostgreSQL (and just about any other "real" RDBMS). These really need to be utilized in OTRS 2.x. I don't see why existing tables can't be migrated over to InnoDB easily. This would allow us to move all these hardcoded data types (attachments, freetext, etc) to "reference tables".
Attachments are not hardcoded with counter. It's only article and ticket free text fields.
-=> I put it on the todo list to do new tests (incl. InnoDB) and in
case to move it to "reference tables".Anyway, thanks for your help! :)
Martin Edenhofer
--
((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg
http://www.otrs.de/ :: Manage your communication!
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
