omnidb/omnidb

Web tool for database management

OmniDB 3.0.3 Beta

Release Date: December 17, 2020

Release Notes

• New features:

  • PostgreSQL 13 support
  • Database structure tree and Properties/DDL tabs with support to additional PostgreSQL objects
  • Option to use Active Directory / LDAP to authenticate OmniDB's users
  • Option to use PostgreSQL as OmniDB's backend database
  • Additional monitoring units
  • Omnis UI helper component (offering walkthroughs)
  • OmniDB's own graphical explain component (displaying Explain and Explain Analyze)
  • Option to share connections between OmniDB users

• Improvements:

  • Core Changes
    • Websocket > Long Polling
    • Better handling of database connections, reusing connection when appropriate
    • Shared tunnels
    • Updated python and javascript libraries (security + stability)
    • Electron > NWJS (New desktop technology)
    • Enhanced shortcuts, allowing users to maintain shortcuts per OS
  • UX/UI improvements for several elements (Connections management, Autocomplete, Global snippet panel with quick-[save/load], contextual menus).

• 3.0.1 changes

  • Bug Fixes
    • Fixed an issue in the long polling mechanism
    • Dark theme colors on autocomplete selection
  • Improvements
    • Added snippets and custom monitoring units to the OmniDB 2 to 3 automatic migration process

• 3.0.2 changes

  • Re-included
    • Explain visualizer component from OmniDB 2.x
    • Shortcuts for issueing Explain and Explain Analyze
  • Bug Fixes
    • Fixed missing dark theme colors on connection results when in full-view
    • Fixed conflict between the z-index of the new explain visualizer and the database tree context menus
  • Improvements
    • Added a toggle to switch between the old and new explain components
    • Improved client-side CPU usage performance (browser rendering gpu-intensive processes)
    • Added a new node-spin loading icon for dark themes with improved visibility

• 3.0.3 changes

  • Bug Fixes
    • Query Tab: Fixed editor key behaviours related to up/down arrows (skipping rows, text selection, text shifting, text indenting)
    • Console Tab: Fixed issue describe command for tables in PostgreSQL 12+
    • Console Tab: Fixed background theme color on console output when changing themes
  • Improvements
    • Reduced chances of having OmniDB being flagged as a threat by security tools (false-positives)
    • Outer Menu: Improved layout and behaviour, providing better awareness of the context
    • Result Grid: Improved resizing behaviours
    • Added password option on --createconnection

Website: https://omnidb.org

Full Documentation: https://omnidb.readthedocs.io

omnidb's Issues

Grant Support

Every table can have privileges granted or revoked to users or roles. This needs to be implemented as a new tab on TableEdit window.
Later, this needs to be implemented on functions and procedures as well.

Move docker image to Alpine

Current docker image is build on ubuntu, will be great to move it to Alpine for fastest deployments.

You can find an attemp in: https://hub.docker.com/r/sorrell/alpine-omnidb/

Export grid data to XLSX, CSV or DBF

Spartacus already can save a DataTable into a XLSX or CSV file (DBF support coming soon).
Maybe a button below SQL editor, next to the data grid?

Store tab information

Users will be able to resume working on OmniDB.

Support to "BLOB" columns (and other data types)

On conversion, it should simply copy all bytes from one database to another.
On select, it should show "Binary Data" on the column, and also offer a way to download it as a file.

Website: Package newest version with Transfer Filter

@rafaelthca, packaged version available for download on OmniDB website doesn't include latest "Transfer Filter" feature. Can you please package the new version to mirror the current repository state?

Show if PK, FK, unique or index is active or not

Connection alias (if exists) on conversion grid

If the connections alias is empty, then use standard way.

Option to create DDL script of the conversion, istead of perming it on a real schema

Couldn't perform conversion from MySQL to PostgreSQL

OmniDB conversion log:

5/10/2016 22:19:37 - Starting conversion.

*** SOURCE DATABASE DATA RETRIEVAL ERROR ***
Error:

[06/10/2016 01:19:38] Spartacus.Database.Exception: Exception of type 'Spartacus.Database.Exception' was thrown. ---. MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'group   union all select count(*) as total, trim('group_category') as table_name' at line 1
at MySql.Data.MySqlClient.MySqlStream.ReadPacket () .0x40c93e20 + 0x001b7. in .filename unknown.:0 
at MySql.Data.MySqlClient.NativeDriver.GetResult (System.Int32& affectedRow, System.Int64& insertedId) .0x40ca2110 + 0x00037. in .filename unknown.:0 
--- End of inner exception stack trace ---

User reported that on MySQL database there is a table called "group" and another table with a field called "order".

Postgress not work without password

how use pg sql without password or stored password(pgadmin)

Copy Leanpub books to GitHub Wiki

OmniConversion: Upsert / Merge feature (sync A -> B)

The idea is asking the user to specify some columns to be a key to link source table with target table.

Then, when a register exists in both source and target tables, the conversion updates the register on target table with source tables' values.

When a register exists in source table and not in target table, the register is transfered from source to target.

When a register exists in target table and not in source table, the register is removed from target table.

Support to Functions and Procedures

Connection Grid: Highlight obligatory fields when user changes the DBMS

Does omnidb support linux ?

Hi,
I love omni and i would like to start using it. Where can i find the linux version, am using ubuntu 14.

OmniConversion: Import data from XLSX, CSV or DBF

Spartacus already can read XLSX, CSV and DBF files. We need to implement a way for user be able to "convert" from those files to any supported RDBMS.
Maybe it's already possible with PollyDB (currently only CSV supported), and in this case PollyDB can be treated as an "RDBMS". But need further investigation.

Update images on Wiki after 1.6

• Some images don't show new "Alias" column in Connection Grid.
• Some images don't show Convert tab.

Find & Replace

It is pretty self explanatory. A simple popup summoned by Ctrl-F. Maybe Ace Editor already has a simple way to accomplish this?

Allow Connections to be given a name

Add a "Name" text box in the Connections window and show it in the Main window, on the DB selection line.

Increase performance using new Spartacus methods QueryList<T> and QuerySList

Show tables from other schemas as graph nodes with another color

Table Edit inside query tab

Show DBMS logo in the Connection Grid

Support to SQL Compact Edition

Redim Panels

MariaDB support apart from MySQL support

They still are pretty close internally, but they might become different.

OmniConversion: Change grid to HandsOnTable

Add autobuild Docker image to dockerhub

Will be great ot have an official docker mage in docker hub for easy deployment & development

Create / Edit Table window: Default value of each column

It should be a new column for each table column, as DEFAULT is SQL ANSI for creation of tables.

Tabs for connections

Support to database migrations

Create a Docker container

Shortcut editor

Hi,

first - thank you for the great tool, keep up the really good work :-)

It would be nice, to edit the shortcuts in a GUI.
F.e.: On Linux (Linux Mint, Firefox) CTRL+Q closes firefox/tab.

Bye
Patrick

OmniConversion: Table / field remap

Data Edit inside query tab

OmniDump

Similar to conversion to SQLite, but storing metadata as well, in order to restore a database identical as it was when the dump was created.
Also the OmniDump will be able to be restored to another RDBMS other than the original RDBMS it was created for.
Also, the OmniDump will be able to be created entirely cryptographed, and in this case can only be restored with a password.

Change graph rendering parameters to optimize it

Support to default value of field on TableEdit window

Enhancement - xlsx as datasource + field adapters

I know this is not vendor neutral and potentially ugly (jet ado driver required... registry hack to be able to read cells with more than 255 characters), but in practice (aka reality), having the ability to use a xlsx spreadsheet as a datasource and import data rows into a db table based on some kind of user-defined mapping is something that would put this tool into the 'must-have' category. Also ugly is there is no concept of schema in a spreadsheet so may not be in scope, but this is a pain point for anyone who's ever had to do it.

Triple ugly-bonus (not limited to just xlsx import)... maybe a "field adapter" override virtual method that offered a programmatic slice of execution context for 'massaging' data prior to committing the row in target table (maybe with the current row in context?)! Might not be feasible if you're only using ddl and no c# during that step... ehh.

In any case, keep up the good work!

Query Parameters

PL/SQL Developer supports parameters on query execution. Parameters are in the form &param_name.

Spartacus already supports parameters in the form #param_name#, so that can be helpful to implement a dynamic popup with all parameters.

Support to IBM DB2

Dark Theme

There are dark themes on the SQL editor, but it would be nice if there was a dark theme on the entire OmniDB screen.

Change conversion status icons

UserGuide: include instructions about how to connect to SQL Server with integrated security

Section 3.4: Creating connections.

OmniConversion: Execute a custom function on some columns of a table in database A, before converting it to database B

UserGuide: Include instructions about connection alias

Prevent browser's default context menu when right clicking inside tree div.

Worst practices / broken by design.

Live schema updates are incompatible with any sort of dev-->staging-->production workflow, even before you consider common scenarios like multiple developers with local schema.

Please take some time to understand why "database migrations" started becoming (widely) popular around 2005 -- and why live schema updates of any sort are a mortifying concept to ops folks everywhere.

Shoot-from-the-hip is incompatible with adhering to SLAs and meeting business needs.

Asynchronous SQL commands

Commands such as queries and executes should not block the interface until they are finished. This will be implemented using threads.