Skip to content

Smart completion tests#4

Closed
j-bennet wants to merge 8 commits into
dbcli:masterfrom
j-bennet:master
Closed

Smart completion tests#4
j-bennet wants to merge 8 commits into
dbcli:masterfrom
j-bennet:master

Conversation

@j-bennet

Copy link
Copy Markdown
Contributor

Added some tests for smart completion.

@amjith

amjith commented Dec 24, 2014

Copy link
Copy Markdown
Member

Thanks for adding the tests. I might squash them into a single commit before merging it in.

@j-bennet

Copy link
Copy Markdown
Contributor Author

How do I do that?
On Dec 23, 2014 10:19 PM, "Amjith Ramanujam" notifications@github.com
wrote:

Thanks for adding the tests. I might squash them into a single commit
before merging it in.


Reply to this email directly or view it on GitHub
#4 (comment).

@amjith

amjith commented Dec 24, 2014

Copy link
Copy Markdown
Member

If you'd like to do it, you can issue:

git rebase -i HEAD~4

That'll pop you into an editor. Then you can squash the commits by changing the word pick to squash.

Then it'll squash the commits into a single commit and you'll get a chance to change the commit message. Then you'll have to force push that new commit to your repo.

@amjith

amjith commented Dec 24, 2014

Copy link
Copy Markdown
Member

I've cherry picked the commit that adds the smart_completion tests. Thank you for the PR.

🍰

@amjith amjith closed this Dec 24, 2014
koljonen added a commit to koljonen/pgcli that referenced this pull request Mar 5, 2017
DiegoDAF added a commit to DiegoDAF/pgcli.daf that referenced this pull request Jul 20, 2026
Port of the review feedback on upstream PR dbcli#1544. Instead of checking
self.force_destructive at both call sites (execute_from_file and
execute_command), confirm_destructive_query now takes a `force` parameter and
owns the whole "should we proceed?" decision:

  non-destructive -> None
  force           -> True
  non-tty stdin   -> None (no prompt)
  otherwise       -> prompt the user

Behaviour is unchanged. The parameter defaults to False, so existing callers
are unaffected. The only remaining self.force_destructive reference is the
guard that suppresses the "Your call!" message, which is about output, not the
proceed/abort decision.

Also closes roadmap item dbcli#4 (Conexiones) in todo.md as redundant: post-connect
SQL and .pg_service.conf already exist, keepalives/connect_timeout already work
via the connection string, and SSL ~ expansion has no practical need.

No version bump (held at 4.5.7 per Diego).
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.

3 participants