"RegExp too big" error
See original GitHub issueIssue type:
[ ] question [x] bug report [ ] feature request [ ] documentation issue
Database system/driver:
[ ] cordova
[ ] mongodb
[ ] mssql
[x] mysql
/ mariadb
[ ] oracle
[ ] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo
TypeORM version:
[x] latest
[ ] @next
[ ] 0.x.x
(or put your version here)
Steps to reproduce or a small repository showing the problem:
Repository to reproduce the error: https://github.com/NicoEnking/typeorm-error
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Error: RegExp too big when running WatchTask... #304 - GitHub
In this case, it sounds like your huge regex is genuinely too big. Searching around the Web yields various results about issues in...
Read more >"Regular Expression is too large" error in PHP - Stack Overflow
Shorten the Regular Expression by using DEFINE for any redundant sub-expressions (see below). Increase the max limit on regex size by re- ...
Read more >global_vars and "regular expression is too large" error
I'm getting a “regular expression is too large” error b/c the $regex value in this loop is a very, very long string. $regex...
Read more >Error: regexp too big. - Twine Q&A
Hello! I have an error that pops in unusual places for an apparently random reason. Does anyone .
Read more >string manipulation - Regular expression too large problem
I just have checked your code with version 10.4 and found that there is no error anymore: the output of StringMatchQ["Bold", pattern] is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Checked your repository and found this issue is resolved in
@next
branch. There are some changes in relation area. Please use@next
version in your project 😃Thanks. I’ll give it a try later on!