Skip to content

Make :username optional configuration argument#7

Merged
rosenfeld merged 1 commit intorosenfeld:masterfrom
janko:make-username-optional
Oct 24, 2022
Merged

Make :username optional configuration argument#7
rosenfeld merged 1 commit intorosenfeld:masterfrom
janko:make-username-optional

Conversation

@janko
Copy link
Contributor

@janko janko commented Oct 24, 2022

When developing locally on Postgres and SQLite, it's common to rely on the default username and have no password, which happens when we create the database with createdb mydatabase on Postgres (on SQLite it's the norm). So, it would be convenient not to have to pass the username. It seems that the database URL generator is already handling the scenario of :username being nil.

This was extracted from #5.

When developing locally on Postgres and SQLite, it's common to rely on
the default username and have no password, which happens when creating
the database with `createdb mydatabase`. So, it would be convenient not
to have to pass the username. It seems that the database URL generator
is already handling the scenario of `:username` being `nil`.
@rosenfeld rosenfeld merged commit e5bf4ec into rosenfeld:master Oct 24, 2022
@rosenfeld
Copy link
Owner

I have no idea why it was required before. Merged, thanks.

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.

2 participants