| Summary | supporting foreign keys between horde tables |
| Queue | Horde Framework Packages |
| Queue Version | Git master |
| Type | Enhancement |
| State | No Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | michael (at) bigmichi1 (dot) de |
| Created | 10/14/2011 (5016 days ago) |
| Due | |
| Updated | 01/30/2013 (4542 days ago) |
| Assigned | |
| Resolved | 01/30/2013 (4542 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Feedback
on it in Horde consumer code, I'm not so sure. We do use InnoDB by
default when creating new tables, but most people migration from
earlier versions might still use MyISAM tables. And we might want to
re-add support for other RDBMs in the future that don't support
foreign keys either.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ supporting foreign keys between horde tables
Type ⇒ Enhancement
State ⇒ New
about adding them to the database layout? mysql uses by default in
horde4 the innodb engine which have also foreign key support. the main
advantage from my point of view is that the schema is clearer to
understand. perhaps it may also simplify the code, because nedd for
consistency checks are done by the db system and so it can go out of
the horde code