Brian,
why do you need both TIMESTAMP and DATETIME?
Do you need fixed CHAR and BINARY as well?
If you have DECIMAL, you need precision and scale also. And precision
may be used for other types: character, binary, time, timestamp.
TEXT should be named CLOB to be aligned with SQL standard...
Add a bool nullable per field.
unique and (primary) key are actually constraints on the table level. If
the constraints are defined on a single column, it is possible to
specify them per-column for convenience. In a canonical form, this might
be placed on the table level.
You also may need character set per column.
Thanks,
Roy
Brian Aker wrote:
Hi!
My roadblock in getting I_S, FRM, etc done is coming up with a new
serialized form of a table definition. I've found that I really like
what Google has done with Protobuffers.
This is the definition I have thus far:
http://drizzle.wikia.com/wiki/Table_Proto_Definition#Current_Definition
Foreign Keys have not been defined yet, and the index definition is
weak. I've put it up on Wikia so that others can take a look at it/offer
up edits. Right now I have defined out all of the types, but it would be
possible to shrink these (aka put a bit in for signed/unsigned... use
collation to define binary or not).
Thoughts? Suggestions? Additions from engine folks?
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
