-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp Hug wrote:
> this patch changes maximum length of column names, index/contraint > names, cursor names and schema names to 128 and keeps MaxUserNameLength > at 30. > it also fixes the metadata to return correct values I have a few questions about this change. 1) For a change like this I would think there would be some functional tests needed and of course documentation changes. So how do they come to be? It would be good to have the functional tests go in with the change and have someone at least signed up to do the doc changes. Otherwise how do we keep track? 2) What are the implications of this change on soft upgrade? 3)If we change the limits what do we do about this line in our charter? "And it also means developers can later migrate to other databases if they so choose." Is it still appropriate? Thanks Kathey -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwdmSG0h36bFmkocRAmceAJ95p/QfuYz3UljEnlLZchCMZR0NywCeOmJ+ ozDu/NRK162zg7Ut+LzoXSo= =2AhR -----END PGP SIGNATURE-----
