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
user-friendly DPB-string in new api [CORE4716] #5023
Comments
Commented by: Doug Chamberlin (greymont) Please pick an established standard for this syntax, such as JSON, rather than using something new! That would answer all the questions from Dimitry, I think. Also, avoid XML as the point is to make the options more readable. |
Commented by: @aafemt Is ODBC standard established enough?.. |
Commented by: Nick (nick) I think... >Comma-separated, zero-separated or semicolon separated? >Why use square braces instead of ODBCstandard braces? >Encoding? wchar_t?.. >How to handle mistyped/unknown parameter names? with error for NoDbTriggers and ProcessName params for FB < 2.1 (they not exists there): with skip NoDbTriggers and ProcessName for FB < 2.1, and skipping SomeFB3Param for FB3: and with plugin params: with skip: |
Commented by: Nick (nick) JSON is good too. |
Commented by: PizzaProgram Ltd. (szakilaci) While this seems to be a great feature at first sight, please consider following aspects too: 2.) Encryption / safety / password protection: 3.) Separating: 4.) Enhancements: |
Submitted by: Nick (nick)
Votes: 2
Now DPB looks like this: #1'?'#1#3'0'#7'WIN1251'#$1C#6'SYSDBA'#$1D#9'masterkey' (in Delphi).
It is not so easy to generate it correctly.
Something like 'ConnectionSqlDialect=[3], ConnectionCharSet=[WIN1251], UserName=[SYSDBA], Password=[masterkey]' seems more friendly.
The text was updated successfully, but these errors were encountered: