Database Management Tools- Part II

We have seen MyWebSQL and DbNinja Database Management Tools in our previous article. Let’s see few more database management tools in this article.


DBeaver is free and open source database management tool. It has the ability to work on different database engines like Oracle, SQLite, Sybase, MySQL, MSSQl among many others.

DBeaver-Database management tool

The following are the features offered by DBeaver:

  • It provides a carefully designed and implemented user interface.
  • Supports multi-platform.
  • Supports databases having JDBC driver.
  • It has the ability to support any external data source which may or may not have a JDBC driver
  • Allow writing various plugins.
  • This application has built with Java. Hence it supports various operating systems such as Linux, Mac, Windows etc.

DBeaver is a free software system. You can redistribute it or modify it under the terms of the Apache License, Version 2.0 (


squel.js-Database Management Tools

JS is an easy to use application. sequel.js is a JavaScript library that helps to build SQL queries in an easier way through object-oriented API. In addition, this application has the ability to customize and support non-standard queries.

Open keyval

Open keyval is free and open source application. It provides unauthenticated access to its server and allows any user to write up to 64 KiB of data to any key. After writing, a read-only version of the key is returned. However, this allows you to provide read-only access to data. The key to the entire system is obscurity. Obscure keys are difficult to guess by other users, and hence they are safe. Read-only keys allow you to assign access to other users without worrying changes made by other users.

Openkeyval-Database Management Tool

OpenKeyval is a simple application. To use it you have to fulfill the following requirements: –

  • You must serve the open keyval directory from the root of your server.
  • Your server needs to support the RewriteRules in .htaccess.
  • The script must be able to write to the data/ subdirectory, which it will try to create in the open keyval directory
  • Invent your own salt to use when hashing values and put it into a file called salt.txt, in the same directory as the source code. This prevents various users from using highlighted tables in the file salt.txt to reverse a read-only key into a writable one.