Bret,
I don't have any problems with such a change. Sensible cleanups in the schema are always welcome. Especially ones that are backward compatible. But: how does RoR treat tinyints without a width specification? I'd rather simply remove all width specifications on the numeric types from the mysql schema (and add the UNSIGNED attribute where possible) since we don't use, need or rely on them at all. Bret Baptist wrote: > We are writing a dbmail administration interface with Ruby on Rails for the > latest dbmail 2.2.9. We are having an issue with the permission column in > dbmail_mailboxes being set to a tinyint(1) in MySQL. Ruby on Rails assumes > that a tinyint(1) in MySQL is a boolean, however dbmail stores values greater > than 1 in that column. If we change the column to be tinyint(2) then Ruby on > Rail has no issues. > > Interestingly there is another column in the dbmail database that stores a > similar value and is a tinyint(3). This is the status column in the > dbmail_messages table. > > What I am wondering is if this change can be made upstream with you guys or > if > we are going to have to maintain the change on our end. > > I would understand completely if you did not want to make this change, I just > think it might be easier for anyone who might want to manipulate the dbmail > database with Ruby on Rails. > > > Thank you very much for your help. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
