Since Sybase, MySQL and MS SQL Server have had support for UNSIGNED
TINYINT for many years (at least for 2 of them), offering support for
an UNSIGNED TINYINT rather than SIGNED at this point makes more sense
and can only be good for Derby's adoption (and that a sufficient reason
for adding it IMHO) (SIGNED TINYINT could always be enabled later _if_
required but JDBC does not require the type to be signed in the first
place) - it brings value for getting Derby more adopted from users
looking to migrate from other known and popular RDBMS (not just from
the ones which got most market shares)...and as far as the footprint as
previously mentioned, it is good to offer support for a 1-Byte datatype
which does matter indeed when running in a small-device environment.
--francois
- Re: [jira] Commented: (DERBY-695) Re-enable the TIN... Francois Orsini
- Re: [jira] Commented: (DERBY-695) Re-enable th... David W. Van Couvering
- Re: [jira] Commented: (DERBY-695) Re-enabl... Daniel John Debrunner
- Re: [jira] Commented: (DERBY-695) Re-e... Rick Hillegas
- Re: [jira] Commented: (DERBY-695) ... Daniel John Debrunner
- Re: [jira] Commented: (DERBY-695) ... Francois Orsini
- Re: [jira] Commented: (DERBY-... Dag H. Wanvik
- Re: [jira] Commented: (DE... Francois Orsini
- Re: [jira] Commented: (DERBY-695) Re-enable th... Satheesh Bandaram
- Re: [jira] Commented: (DERBY-695) Re-enable th... Rick Hillegas
