Tim Soderstrom wrote:
Actually, I'm the opposite. I like having specific types for this. It
makes is abundantly clear and well defined by calling it something
other than an integer. Yes, at least in this case, it's an integer,
but that doesn't mean you should add it to other integers, like
Salary, or something. It seems like if you use a modifier to an
integer, all that becomes less clear. Plus, if Drizzle uses custom
types for this, it would make more sense if other people wanted to
make their own sequence types.
$0.02
Consider the impact on foreign keys. If the primary key has to be a
funny data type that reflects it's initialization (!), then the foreign
key must be something else. Now there isn't an intrinsic problem with
allowing/requiring primary and foreign keys to be different types, but
it's something I think you will serious regret.
I revert to my position that data type should reflect the classes of
operations and conversions that can be performed on a particularly
type. You can add numbers, concatenate strings, and convert dates to
Julian values. Data types should not be used for other purposes.
If you want something "type-ish", implement SQL domains.
--
Jim Starkey
President, NimbusDB, Inc.
978 526-1376
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
