Error: "direct" is not a valide option name for MySQL UniProvider

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
kerbadoughazali
Posts: 10
Joined: Fri 28 Jul 2017 09:20

Error: "direct" is not a valide option name for MySQL UniProvider

Post by kerbadoughazali » Sun 06 Aug 2017 10:28

Hello,
i have the new version of UniDAC 7.0.1 Professional,
i made this to connect:

Code: Select all

    
    UniConnection1.ProviderName := 'MySQL';
    UniConnection1.SpecificOptions.Values['Direct'] := 'True';
    UniConnection1.Server   := serverEdit.Text;
    UniConnection1.Database := dbEdit.Text;
    UniConnection1.Username := userEdit.Text;
    UniConnection1.Password := pwEdit.Text;
    UniConnection1.Port          := 3306;
    UniTable1.TableName        := tableEdit.Text;
    UniConnection1.LoginPrompt := False;
    UniConnection1.Connect;
but after cliqing a connect button this message appeared:
"direct" is not a valide option name for MySQL UniProvider
how fix it?

ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Error: "direct" is not a valide option name for MySQL UniProvider

Post by ViktorV » Mon 07 Aug 2017 10:12

We have removed the specific option "Direct" for the MySQL provider, because all the functionality of our components is supported in Direct Mode, and performance is higher in comparison to using client library. Some features are not supported not in Direct Mode. UniDAC connects to MySQL server directly in Direct Mode, avoiding MySQL client library.

kerbadoughazali
Posts: 10
Joined: Fri 28 Jul 2017 09:20

Re: Error: "direct" is not a valide option name for MySQL UniProvider

Post by kerbadoughazali » Mon 07 Aug 2017 14:57

hi, after removed the Direct mode in my connection, no the message "connection is not defined" appeared!

ViktorV
Devart Team
Posts: 3168
Joined: Wed 30 Jul 2014 07:16

Re: Error: "direct" is not a valide option name for MySQL UniProvider

Post by ViktorV » Mon 07 Aug 2017 15:23

The 'Connection is not defined' error means that you did not define a connection for a dataset for which you are trying to open. To solve the problem, you should set the Connection property of the dataset. Example:

Code: Select all

  UniTable1.Connection := UniConnection1;
If this does not help in resolving the problem, please create a small sample demonstrating the issue and send it to us via form e-support: https://www.devart.com/company/contactform.html

Post Reply