| Bug #34258 | Regex Importer Can only handle 10 expression segments | ||
|---|---|---|---|
| Submitted: | 3 Feb 2008 0:51 | Modified: | 4 Mar 2008 12:01 |
| Reporter: | Peter A | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
| Version: | 1.2.12 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | expressions, import, regex | ||
[4 Feb 2008 12:01]
Sveta Smirnova
Thank you for the report. Please check if this is duplicate of bug #28636 and if you are not agree, provide better "how-to-repeat" description
[5 Mar 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: When the text you're parsing requires more than 10 expression components, it parses correctly, but there's no way to address the 11th component. If you insert a substitution string such as '$RegEx1.11' it inserts the contents of expression 1 with the character '1' appended. It is as if you had typed '$RegEx1.1' + '1' How to repeat: create an expression with more than 10 components and try to assign the 11th component to a column while exporting Suggested fix: also allow an expression delimiter such as '{' for compound substitutions e.g. '${RegEx1.11}x' to use the 11th field and append an x.