Skip to content

Conversation

kev1N916
Copy link

PR Info

Closes #2647

Bug Fixes

Fixes the bug where we are not able to connect to the postgres database when the url is given in the postgres:db_name format.

Signed-off-by: involk-secure-1609 <[email protected]>
@kev1N916 kev1N916 changed the title supports postgres:db_name now Allows support for postgres:db_name format Oct 13, 2025
})
.next()
.unwrap();
let database_name = match url.path_segments() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you move this logic into a separate function and write a unit test to ensure we get the correct database name?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If unit tests for this already exist, please let me know.

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.

Invalid error "There is no database name as part of the url path" for a db url postgres:dbname when running sea-orm-cli generate entity

2 participants