OracleConnection lost password since using dotConnect 7.9 + EF 6 RC1
Posted: Wed 11 Sep 2013 09:55
Hello Everybody.
I'm using dotConnect for oracle 7.9 + EF 6.0 RC1 / Code First.
I'm using a OracleConnection singleton instance to connect all provider to the database.
It's work fine.
Since I use new Entity Framework (6.0 Beta -> 6.0 RC1) and new dotConnect (oracle 7.8 -> oracle 7.9) I cannot connect to the database more than once.
When I see the instance of OracleConnection.ConnectionString after setting it, it contains the password to the database.
After EF migration is called (verify base strucutre and update if needed) that use this instance of DbConnection, the OracleConnection.ConnectionString is changed and the password is lost: next try to connect to the database indicate : ORA-01005: null password given; logon denied.
If I create the OracleConnection instance each time, it's work fine. What about the way to use the same OracleConnection instance to don't lost password on it ?
I don't know if this bug (is it really a bug) is from dotConnect side or Entity Framework side.
Any idea ?
Thank for your reply.
I'm using dotConnect for oracle 7.9 + EF 6.0 RC1 / Code First.
I'm using a OracleConnection singleton instance to connect all provider to the database.
It's work fine.
Since I use new Entity Framework (6.0 Beta -> 6.0 RC1) and new dotConnect (oracle 7.8 -> oracle 7.9) I cannot connect to the database more than once.
When I see the instance of OracleConnection.ConnectionString after setting it, it contains the password to the database.
After EF migration is called (verify base strucutre and update if needed) that use this instance of DbConnection, the OracleConnection.ConnectionString is changed and the password is lost: next try to connect to the database indicate : ORA-01005: null password given; logon denied.
If I create the OracleConnection instance each time, it's work fine. What about the way to use the same OracleConnection instance to don't lost password on it ?
I don't know if this bug (is it really a bug) is from dotConnect side or Entity Framework side.
Any idea ?
Thank for your reply.