OdbcConnection String
To establish an odbc Connection String in a Method, one could do it the following way:
odbcConnection = new OdbcConnection();
odbcConnection.Connection = "DRIVER=MySQL ODBC 5.2w Driver;"
+ "SERVER=localhost;PORT=3306;"
+ "DATABASE=dbdemo2;UID=demo-user";
Why does the DRIVER need to be mentioned in curly brackets ?
c# odbc database-connection
add a comment |
To establish an odbc Connection String in a Method, one could do it the following way:
odbcConnection = new OdbcConnection();
odbcConnection.Connection = "DRIVER=MySQL ODBC 5.2w Driver;"
+ "SERVER=localhost;PORT=3306;"
+ "DATABASE=dbdemo2;UID=demo-user";
Why does the DRIVER need to be mentioned in curly brackets ?
c# odbc database-connection
add a comment |
To establish an odbc Connection String in a Method, one could do it the following way:
odbcConnection = new OdbcConnection();
odbcConnection.Connection = "DRIVER=MySQL ODBC 5.2w Driver;"
+ "SERVER=localhost;PORT=3306;"
+ "DATABASE=dbdemo2;UID=demo-user";
Why does the DRIVER need to be mentioned in curly brackets ?
c# odbc database-connection
To establish an odbc Connection String in a Method, one could do it the following way:
odbcConnection = new OdbcConnection();
odbcConnection.Connection = "DRIVER=MySQL ODBC 5.2w Driver;"
+ "SERVER=localhost;PORT=3306;"
+ "DATABASE=dbdemo2;UID=demo-user";
Why does the DRIVER need to be mentioned in curly brackets ?
c# odbc database-connection
c# odbc database-connection
asked Nov 12 '18 at 23:15
MT.SMT.S
154
154
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
From the documentation
OdbcConnection.ConnectionString Property
connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string
empty-string ::=
attribute ::= attribute-keyword=attribute-value | DRIVER=[]attribute-value[]
attribute-keyword ::= DSN | UID | PWD
| driver-defined-attribute-keyword
attribute-value ::= character-string
driver-defined-attribute-keyword ::= identifier
Gets or sets the string used to open a data source.
...
Applications do not have to add braces around the attribute value after the Driver keyword unless the attribute contains a semicolon
(;), in which case the braces are required. If the attribute value
that the driver receives includes braces, the driver should not remove
them but they should be part of the returned connection string.
A DSN or connection string value enclosed with braces () that contains any of the characters (),;?*=!@ is passed intact to the
driver. However, when you use these characters in a keyword, the
Driver Manager returns an error when you work with file DSNs, but
passes the connection string to the driver for regular connection
strings. Avoid using embedded braces in a keyword value.
The connection string may include any number of driver-defined
keywords. Because the DRIVER keyword does not use information from the
system, the driver must define enough keywords so that a driver can
connect to a data source using only the information in the connection
string. The driver defines which keywords are required to connect to
the data source.
In this case it probably doesn't need it, though there is no harm in adding braces
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271479%2fodbcconnection-string%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the documentation
OdbcConnection.ConnectionString Property
connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string
empty-string ::=
attribute ::= attribute-keyword=attribute-value | DRIVER=[]attribute-value[]
attribute-keyword ::= DSN | UID | PWD
| driver-defined-attribute-keyword
attribute-value ::= character-string
driver-defined-attribute-keyword ::= identifier
Gets or sets the string used to open a data source.
...
Applications do not have to add braces around the attribute value after the Driver keyword unless the attribute contains a semicolon
(;), in which case the braces are required. If the attribute value
that the driver receives includes braces, the driver should not remove
them but they should be part of the returned connection string.
A DSN or connection string value enclosed with braces () that contains any of the characters (),;?*=!@ is passed intact to the
driver. However, when you use these characters in a keyword, the
Driver Manager returns an error when you work with file DSNs, but
passes the connection string to the driver for regular connection
strings. Avoid using embedded braces in a keyword value.
The connection string may include any number of driver-defined
keywords. Because the DRIVER keyword does not use information from the
system, the driver must define enough keywords so that a driver can
connect to a data source using only the information in the connection
string. The driver defines which keywords are required to connect to
the data source.
In this case it probably doesn't need it, though there is no harm in adding braces
add a comment |
From the documentation
OdbcConnection.ConnectionString Property
connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string
empty-string ::=
attribute ::= attribute-keyword=attribute-value | DRIVER=[]attribute-value[]
attribute-keyword ::= DSN | UID | PWD
| driver-defined-attribute-keyword
attribute-value ::= character-string
driver-defined-attribute-keyword ::= identifier
Gets or sets the string used to open a data source.
...
Applications do not have to add braces around the attribute value after the Driver keyword unless the attribute contains a semicolon
(;), in which case the braces are required. If the attribute value
that the driver receives includes braces, the driver should not remove
them but they should be part of the returned connection string.
A DSN or connection string value enclosed with braces () that contains any of the characters (),;?*=!@ is passed intact to the
driver. However, when you use these characters in a keyword, the
Driver Manager returns an error when you work with file DSNs, but
passes the connection string to the driver for regular connection
strings. Avoid using embedded braces in a keyword value.
The connection string may include any number of driver-defined
keywords. Because the DRIVER keyword does not use information from the
system, the driver must define enough keywords so that a driver can
connect to a data source using only the information in the connection
string. The driver defines which keywords are required to connect to
the data source.
In this case it probably doesn't need it, though there is no harm in adding braces
add a comment |
From the documentation
OdbcConnection.ConnectionString Property
connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string
empty-string ::=
attribute ::= attribute-keyword=attribute-value | DRIVER=[]attribute-value[]
attribute-keyword ::= DSN | UID | PWD
| driver-defined-attribute-keyword
attribute-value ::= character-string
driver-defined-attribute-keyword ::= identifier
Gets or sets the string used to open a data source.
...
Applications do not have to add braces around the attribute value after the Driver keyword unless the attribute contains a semicolon
(;), in which case the braces are required. If the attribute value
that the driver receives includes braces, the driver should not remove
them but they should be part of the returned connection string.
A DSN or connection string value enclosed with braces () that contains any of the characters (),;?*=!@ is passed intact to the
driver. However, when you use these characters in a keyword, the
Driver Manager returns an error when you work with file DSNs, but
passes the connection string to the driver for regular connection
strings. Avoid using embedded braces in a keyword value.
The connection string may include any number of driver-defined
keywords. Because the DRIVER keyword does not use information from the
system, the driver must define enough keywords so that a driver can
connect to a data source using only the information in the connection
string. The driver defines which keywords are required to connect to
the data source.
In this case it probably doesn't need it, though there is no harm in adding braces
From the documentation
OdbcConnection.ConnectionString Property
connection-string ::= empty-string[;] | attribute[;] | attribute; connection-string
empty-string ::=
attribute ::= attribute-keyword=attribute-value | DRIVER=[]attribute-value[]
attribute-keyword ::= DSN | UID | PWD
| driver-defined-attribute-keyword
attribute-value ::= character-string
driver-defined-attribute-keyword ::= identifier
Gets or sets the string used to open a data source.
...
Applications do not have to add braces around the attribute value after the Driver keyword unless the attribute contains a semicolon
(;), in which case the braces are required. If the attribute value
that the driver receives includes braces, the driver should not remove
them but they should be part of the returned connection string.
A DSN or connection string value enclosed with braces () that contains any of the characters (),;?*=!@ is passed intact to the
driver. However, when you use these characters in a keyword, the
Driver Manager returns an error when you work with file DSNs, but
passes the connection string to the driver for regular connection
strings. Avoid using embedded braces in a keyword value.
The connection string may include any number of driver-defined
keywords. Because the DRIVER keyword does not use information from the
system, the driver must define enough keywords so that a driver can
connect to a data source using only the information in the connection
string. The driver defines which keywords are required to connect to
the data source.
In this case it probably doesn't need it, though there is no harm in adding braces
answered Nov 12 '18 at 23:20
TheGeneralTheGeneral
28k63365
28k63365
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271479%2fodbcconnection-string%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown