Roy Lyseng wrote:
Patrick Galbraith wrote:
Hi all,
I've unfortunately been super busy with other things going on in the
last month of so and have missed out on some changes. I'm working at
the moment on DBD::drizzle, and notice that it seems the types have
been consolidated (?) This is what I see now:
num enum_field_types { DRIZZLE_TYPE_TINY,
DRIZZLE_TYPE_LONG,
DRIZZLE_TYPE_DOUBLE,
DRIZZLE_TYPE_NULL, DRIZZLE_TYPE_TIMESTAMP,
DRIZZLE_TYPE_LONGLONG,
DRIZZLE_TYPE_TIME,
DRIZZLE_TYPE_DATETIME,
DRIZZLE_TYPE_NEWDATE, DRIZZLE_TYPE_VARCHAR,
DRIZZLE_TYPE_VIRTUAL,
DRIZZLE_TYPE_NEWDECIMAL,
DRIZZLE_TYPE_ENUM,
DRIZZLE_TYPE_BLOB,
DRIZZLE_TYPE_MAX=DRIZZLE_TYPE_BLOB
This is the extent of types, right?
NULL is not a type...
Strictly speaking, you are correct. But life is vastly simpler if you
add it to the type list.
There is VARCHAR and BLOB, but no VARBINARY and CLOB. Lack of
orthogonality?
A clob is a blob known to contain UTF-8 and therefore subject to client
side conversion. It is a very important type.
I regret that I concur on VARBINARY.
VIRTUAL is a property of a field, not a type.
Even a virtual field has to have a type, so VIRTUAL as type doesn't buy
you anything.
And a related subject, I hope somebody has gotten rid of the MySQL
decimal type in favor of something more reasonable. Just because the
precision is stated in decimal is no excuse to store it internally in
decimal and even less reason to store as two separate numbers, one for
each side of the decimal point. Whoever invented that dog must have
missed school the day they covered fractions.
Falcon has a large precision binary with decimal scale factors that
dirzzle might lift.
--
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
