Greg, It is very normal to have 255 as varchar lengths. 128 is odd, since this is actually a direct power of 2, and varchars typically reserve one special character slot for EOS markers.
I would go varchar 255 unless you *know* it will be shorter, or *think* it might be longer. Since varchars are dynamically assigned, the DB (generally) doesn't grow by having larger varchars defined. Chris On Wed, 10 Oct 2012 15:55:28 -0600 Greg Logan <[email protected]> wrote: > Hi folks, > > In getting ready to cut the RC (not today, sorry Judy!), I noticed > that the annotation bundle doesn't create its table correctly in > MySQL. This is filed as MH-8971. The big issue slowing this down is > that we haven't decided on a set mediapackage ID size. The default > in a lot of places is 36, which is the right size for the UUID > generated by the system, but too small for an unscheduled capture. > Looking at our DDLs right now, I see sizes of 128, 255 (both MySQL > VARCHARs), and 65535 (both as a MySQL TEXT and MySQL VARCHAR, with > the latter not functional). > > I'm planning on cutting the next 1.4 RC tomorrow, so as a temporary > fix I will change the mediapackage IDs column lengths to 128 across > the board. Does anyone have any need for a longer column length than > that? If not, this temporary fix may become permanent! > > G > -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
