Hi!
On Nov 17, 2009, at 1:45 PM, Jay Pipes wrote:
My vote is toss an error:
a) When t1's engine is temporary and t2's engine is not specified.
b) When t1's engine is temporary and t2's specified engine cannot
handle regular tables.
I prefer explicit over implicit and therefore vote against letting
the t2 table's storage engine default to the default storage
engine. We're talking about DDL operations here, not every-day
stuff that would be a pain in the butt to type out the ENGINE=XXX
clause.
I believe I agree with the above. We added the feature to have engine=
as an argument for CREATE TABLE LIKE to get around an inconsistency
when selecting from I_S, so it will be possible to create a table from
an engine which is TEMP only to one which is not.
Cheers,
-Brian
BTW I found this out because I finished up the patch to ditch most of
store_lock() :)
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
