Skip to content

Conversation

@tianvan
Copy link

@tianvan tianvan commented Mar 7, 2024

When both Connection and ConnectionString are not null, Connection's ConnectionString is different to ConnectionString, the ConnectionString will be used instead of the Connection's ConnectionString.

It will cause a bug, for example, I need to create database through following code:

DbContext.Database.Migrate()

if DatabaseSource is Setted:

extension.WithDataSource(dataSource);

then we set AdminDatabase:

extension.WithAdminDatabase("postgres");

it wont work.

When both Connection and ConnectionString are not null, Connection's ConnectionString is different to ConnectionString, the ConnectionString will be used instead of the Connection's ConnectionString.

It will cause a bug, for example, I need to create database through following code:

```csharp
DbContext.Database.Migrate()
```
if DatabaseSource is Setted:

```csharp
extension.WithDataSource(dataSource);
```
 then we set AdminDatabase:

```csharp
extension.WithAdminDatabase("postgres");
```
it wont work.
@tianvan tianvan changed the title Syncing Connection and ConnectionString fix the bug that AdminDatabase Setting is invalid when Both DataSource is setted. Syncing Connection and ConnectionString fix the bug that AdminDatabase Setting is invalid when DataSource is setted. Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant