Bug #11391 | Create table 2e2 fails, not documented | ||
---|---|---|---|
Submitted: | 16 Jun 2005 17:03 | Modified: | 23 Jun 2005 18:26 |
Reporter: | Jeremy Cole (Basic Quality Contributor) (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | All | OS: | |
Assigned to: | Stefan Hinz | CPU Architecture: | Any |
[16 Jun 2005 17:03]
Jeremy Cole
[16 Jun 2005 17:19]
Kolbe Kegel
Either behavior needs to be changed (preferable) or documentation needs to be updated to explicitly outline this case.
[23 Jun 2005 18:26]
Mike Hillyer
Documentation updated as follows, should hopefully make things a bit more clear: <para> It is recommended that you do not use names of the pattern <literal><replaceable>X</replaceable>e<replaceable>X</replaceable></literal>, such as <literal>1e</literal> or <literal>2e2</literal>, because an expression like <literal>1e+1</literal> is ambiguous. It might be interpreted as the expression <literal>1e + 1</literal> or as the number <literal>1e+1</literal>, depending on context. </para> <para> Be careful when using <literal>MD5</literal> to produce table names, as it can produce illegal tables names such as the ones listed above. </para>