Monty Taylor wrote:
Jim Winstead wrote:
On Wed, Dec 17, 2008 at 1:40 PM, Brian Moon <[email protected]> wrote:
For Phorum, I would not. In the current MySQL world, I would like to have
people that have InnoDB use it. So, the create statements show InnoDB.
But, if it is not on the server, well, this would be bad. It helps that
MySQL falls back to the default table type.
Make sense? Any solutions come to mind for this case?
Well, in this _specific_ case, I wouldn't worry about it since we're not
planning on shipping drizzle without innodb at the moment, and it is the
default engine. However -
something like 'CREATE TABLE ... ENGINE = INNODB OR MYISAM' might be nice.
or 'CREATE TABLE ... ENGINE = INNODB OR DEFAULT'.
or maybe a way to declare whether you need a certain type of engine,
but aren't particular about which one. 'CREATE TABLE .. ENGINE =
TRANSACTIONAL'
I sort of like both of the above. In general, if someone (like Phorum)
is shipping something, they'd like for install scripts to be able to say
"create this preferrably in InnoDB, but any trans table is better than
any non-trans table... but really, give us what you've got" I'm guessing
that this isn't an isolated thing for open source projects that use
databases.
For this purpose, I would rather suggest a separate statement (e.g.,
setting a system variable) that change what is the default storage
engine. That way, one could let the CREATE TABLE statements be "storage
engine agnostic" (i.e., not include engine specification).
Of course, we could also ship a simple capabilities tool or function or
something that installers like Phorums could use to determine what
storage engine they should use...
--
Øystein Grøvlen, Senior Staff Engineer
Sun Microsystems, Database Group
Trondheim, Norway
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
