Add Database Tools

[mgramin]

https://github.com/mgramin/awesome-db-tools

This is a community driven list of database tools (ide, cli, managing, monitoring, migrations, modellers, visualization etc)

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

[sindresorhus]

Don't open a Draft / WIP pull request

[animator]

Hi,
I reviewed the PR and my comments are as follows:

• The name of the list "Database Tools" is misleading in the sense that it covers majorly SQL Databases (primarily Postgres with a few references to MySQL and Oracle tools). It lacks mentioning any tools in the NoSQL paradigm or any Big Data Database tools. I know it is a difficult task to get everything under the same roof, but you should reconsider renaming the list in case you want to go ahead with the current content.
• I like how you have segregated different tools based on their utility, but for a database user this list is kind of a maze right now. I recommend the following improvements:
  • There are tools which are database specific and some which are cross-database. So instead of the current sections (IDE, GUI Managers/Clients, CLI tools, DB-schema navigation and visualization Modelers, .. ... ), the list should be presented as (Cross platform, Postgres, MySQL, Oracle, ...). For each database section (eg: Postgres) there should be sub-sections like (IDE, GUI Managers/Clients, CLI tools, DB-schema navigation and visualization Modelers, .. ... ). This will help a particular database user to directly jump to the required section.
  • Also, if a user is an expert in a particular database (for example in my case Teradata and Netezza which is not widely used), he can easily contribute to the list and extend it if it is structured as discussed above.

[GustavBertram]

You should review the guidelines again. You're missing something of an equine nature.

[Jogai]

You should review the guidelines again. You're missing something of an equine nature.

This took me way to long to realize what you meant...

[mgramin]

Reviewed PRs: #1681, #1676

[mgramin]

unicorn

[alexesprit]

Here are things should be fixed:

• Missing license file
• Invalid header levels
• License name in readme file
• Invalid table of contents

Not sure if it's an issue, but I think the main header should be first:

# Awesome Database Tools [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)

> Community driven list of database tools

[alexesprit]

Aside swapping the main header and the description, LGTM.

[alexesprit]

Also, I think the badge URL in readme should be: https://awesome.re/badge.svg

[mgramin]

Aside swapping the main header and the description, LGTM.

@alexesprit Thanks, fixed.

[mgramin]

Also, I think the badge URL in readme should be: https://awesome.re/badge.svg

@alexesprit Thanks, fixed.

[mgramin]

@animator Hi, thanks for your review.

• This list contains both SQL and noSQL tools (e.g. Tabix, HouseOps, Robo 3T, dbKoda etc). Unfortunately, at the moment there are much more awesome SQL tools than noSQL tools.
• The description of each tool should contain the name of the supported database. If there is no specific database name, it is assumed that the tool supports several different databases.

[mgramin]

🦄

[chrislatorres]

It looks like there is a formatting error here at:

DBdeployer - Tool that deploys MySQL database servers easily. -dbatools - PowerShell module that you may think of like a command-line SQL Server Management Studio.

[mgramin]

It looks like there is a formatting error here at:

DBdeployer - Tool that deploys MySQL database servers easily. -dbatools - PowerShell module that you may think of like a command-line SQL Server Management Studio.

Thanks, fixed

[mgramin]

Hi @sindresorhus, I fixed all detected problems. Could you please take a look at this PR?

[sindresorhus]

Tweet: https://twitter.com/awesome__re/status/1246779641475424256