| Summary | Create MySQL 5 SQL scripts using VARCHAR(MAX) |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | chuck (at) horde (dot) org |
| Created | 8/2/08 (6460 days ago) |
| Due | |
| Updated | 7/28/11 (5370 days ago) |
| Assigned | |
| Resolved | 7/28/11 (5370 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
State ⇒ Feedback
Version ⇒ Git master
chose between varchar(max) and blob in migration while still keep it
compatible with other DBs?
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ Create MySQL 5 SQL scripts using VARCHAR(MAX)
Type ⇒ Enhancement
State ⇒ Accepted
tables don't really need BLOB-size data size - horde_perms.perm_data
for example. With MySQL 5, VARCHARs can be nearly 64k, which is
plenty, and per http://arjen-lentz.livejournal.com/126316.html, will
prevent some temp table usage which will speed up permissions queries.
We should create db-specific fields that make use of that -
.mysql5.sql for example - for relevant databases.