[MDEV-6026] MySQL Bug #11757397 49437: CANNOT DO SHOW FIELDS FOR BIG VIEW Created: 2014-04-04  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.10
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Sergey Vojtovich Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-4784 merge test cases from 5.6 Stalled

 Description   

Test case for MySQL "Bug #11757397 49437: CANNOT DO SHOW FIELDS FOR BIG VIEW" fails in 10.0. Please check if the problem affects MariaDB: it could have been fixed differently.

revno: 3256
committer: Jon Olav Hauglid <jon.hauglid@oracle.com>
branch nick: mysql-trunk-bug11757397
timestamp: Wed 2011-07-13 12:29:51 +0200
message:
  Bug #11757397 49437: CANNOT DO SHOW FIELDS FOR BIG VIEW
 
  The problem was that views with too many columns in some
  cases would appear to work correctly, while in other cases gave
  various error messages. For example, DESCRIBE and SHOW commands
  could give "Incorrect key file for table..." errors.
 
  Depending on column datatypes used, views are materialized
  as either MyISAM or Memory internal temporary tables.
  The root cause of the problem was that MyISAM tables support
  a limited number of columns. This is due too a 64K file header
  size limitation. This limitation was not checked by CREATE VIEW.
  Therefore views with unsupported sizes could be made, leading to
  various errors when the view was later used.
 
  This patch fixes the problem by reporting ER_TOO_MANY_FIELDS
  error ("Too many columns") if views with more than 4096 columns
  are created. Thus ensuring that any MyISAM table which might
  be created for view processing will fit into the 64K header limit.
  Note that 4096 was chosen as limit as this number is already the
  limit on the number of columns for base tables.
 
  Test case added to view.test.


Generated at Thu Feb 08 07:08:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.