Bug #54907 | Cannot know current row_format, after row_format specification fails. | ||
---|---|---|---|
Submitted: | 30 Jun 2010 7:46 | Modified: | 1 Jul 2010 0:46 |
Reporter: | Yoshiaki Tajika (Basic Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB Plugin storage engine | Severity: | S3 (Non-critical) |
Version: | 5.1.48, 5.1.49-bzr | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | qc |
[30 Jun 2010 7:46]
Yoshiaki Tajika
[30 Jun 2010 9:21]
Valeriy Kravchuk
Verified just as described with recent 5.1.49 from bzr on Linux.
[30 Jun 2010 11:28]
Mikhail Izioumtchenko
could you clarify where the bug is? I don't see any. +------------+-----------------------+ | row_format | create_options | +------------+-----------------------+ | Compact | row_format=COMPRESSED | +------------+-----------------------+ the column row_format is Compact just as what CREATE TABLE ordered. the column create_options is row_format=COMPRESSED just as the CREATE options the user specified. The fact that row_format had to be changed to compact doesn't make any less true the fact that row_format=COMPRESSED was used in CREATE TABLE.
[30 Jun 2010 23:56]
Yoshiaki Tajika
I'm sorry. Your explanation let me notice a mistake in my understanding. Would you please change the status into 'not a bug' or something like that?
[1 Jul 2010 0:46]
Calvin Sun
Change to Not a Bug per user request.