-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[Fix] Can't parse db name in .env file #3083
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Can't parse db name in .env file when trying to bypass the password. Below is the detailed issue link. sqlitebrowser#3081
|
So if my poor regular expression knowledge is good, it was only accepting a-z (both lower and uppercase), 0-9, period, dash and underscrore, and now you've added @. |
...and we haven't even broached unicode characters in filenames... |
|
can-of-worms.gif 😂 |
|
Yes, this Pull Request can't solve other special symbols. I think maybe something like below may solve all the special symbols (except '=') |
|
Merged. Thanks, @Sitlos. |
Custom format is not loading the fields and implementation is not justified as the .env format is basically a simplification of the IniFormat. Tested with: - Built for x86_64-little_endian-lp64, running on x86_64 - Qt Version 5.15.3 - SQLCipher Version 3.4.1 (based on SQLite 3.15.2). Tested no regression for #3083.
Custom format is not loading the fields and implementation is not justified as the .env format is basically a simplification of the IniFormat. Tested with: - Built for x86_64-little_endian-lp64, running on x86_64 - Qt Version 5.15.3 - SQLCipher Version 3.4.1 (based on SQLite 3.15.2). Tested no regression for #3083.
Custom format is not loading the fields and implementation is not justified as the .env format is basically a simplification of the IniFormat. Tested with: - Built for x86_64-little_endian-lp64, running on x86_64 - Qt Version 5.15.3 - SQLCipher Version 3.4.1 (based on SQLite 3.15.2). Tested no regression for #3083.
Can't parse db name in .env file when trying to bypass the password. Below is the detailed issue link.
#3081