build_name length

[Joe Marcus Clarke]

On Thu, 2009-03-19 at 00:31 +0300, Dmitry Morozovsky wrote:
> On Wed, 18 Mar 2009, Dmitriy Kirhlarov wrote:
> 
> DK> We are using tinderbox for fixing package list for types of our FreeBSD
> DK> installations.
> DK> With this reason I woud like to use meaningfull build names with type of
> DK> installation, architecture, build date, etc (something like
> DK> MailFrontend-amd64-7.1-20090318-1.1.2). Description field not very usefull,
> DK> because, I can't use it with pkg_add, when installing new host.
> DK> 
> DK> Currently, builds.build_name field is varchar(32) NOT NULL.
> DK> Could you, please, extend this field up to varchar(255) in next release?
> 
> I don't know much 'bout current MySQL, but otherwise -- wouldn't it be more 
> useful to just define is as text?

TEXT is probably excessive (65535).  However, a VARCHAR(255) is not
necessary a bad idea.  However, the longer you make these names, the
more risk of running into bad formatting in the webui.

Joe

> 
-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://marcuscom.com/pipermail/tinderbox-list/attachments/20090319/6d290553/attachment.bin>