ODataDB can be used as a database data editor without any configuration.
Basic features include:
- Getting data from tables, views, and procedures
- Saving data changes to tables and views
- Changing procedure parameters
- Replacing IDs with names from primary key tables
- Copying and pasting ranges
- Undo and redo actions
- Sorting rows by multiple columns
- Hiding and displaying columns
- Aligning columns
- Formatting numeric values
- Calendar for entering dates
- Multilingual interface
- Embedding in corporate web pages
In general, we have tried to provide the required minimum of Microsoft Excel functionality for working with data.
The screenshot shows getting data from a stored procedure that can be saved to a source data table.
ODataDB also identified primary key tables of the accounts, items, and companies, and generated value lists for parameters and cells.
To get such an editor, just add the database connection string.
Customizable features for creating corporate web applications
By configuring on the server-side, ODataDB gets the following features:
- Saving data by stored procedures
- Checking and saving data when cells are changed
- Configuring regular and dynamic lists of parameter values
- Configuring regular and dynamic lists of values in cells
- Using SQL code anywhere as stored procedures
- Translating object names, fields, and parameters
- Translating user data
- Loading table formats from a database
- Conditional formatting
ODataDB features, for example, are sufficient for working in budgeting and planning applications.
The screenshot shows an example of budget reports.
Data, formatting, parameter values, translation of column names and parameters are loaded from the database.
You can try ODataDB with the applications online:
Basic ideas of ODataDB
To start ODataDB, add an anonymous database connection string.
When the server-side receives a user request,
it connects to the database under the user's username and password,
reads metadata and creates the OData 4.0 service based on user permissions in the database.
After that, the server-side serves OData queries and executes SQL commands
SELECT, INSERT, UPDATE, DELETE, or EXEC under the user's credentials.
Since ODataDB uses a shared data layer and settings with the SaveToDB add-in,
it gets rich and compatible application configuration options.
The server-side is implemented with ASP.NET Core 3.1 and supports Windows and Linux.
It can work as a console application, a Windows service,
and also under IIS, IIS Express, Apache, and Nginx web servers.
It supports Microsoft SQL Server, Oracle Database, DB2, MySQL, MariaDB, PostgreSQL, and NuoDB.
What is the difference between ODataDB and DBGate?
Therefore, the interface features are the same for both products.
The server parts also use common components, but they differ significantly.
DBGate uses a simple model for converting HTTP requests to SQL commands.
ODataDB implements a full-fledged model based on the OData standard and supports most of the features of the standard.
For example, it supports using the batch mode of updates within a transaction, and the $ filter function with different operators.
Because of this, ODataDB can be used out of the box with other OData clients, such as Microsoft Excel or Microsoft Power Query.
Who is ODataDB for?
ODataDB targets database developers who can create full-fledged corporate web applications with ODataDB.
Applications are configured by editing configuration tables in a database
and creating database objects, for example, to get lists of values or save data.
Also, ODataDB would be useful for current customers of the SaveToDB add-in,
since, within an hour, they can get an additional web application
due to the compatibility of the configuration of the SaveToDB add-in and ODataDB.
How much does it cost, and is there a free version?
The free edition of ODataDB has a limit on two users.
The price of a perpetual license is 3,600 USD for use on up to five servers.
We also recommend purchasing the warranty (20% of the price) to upgrade to the next major versions at no additional cost.
How to start?
We recommend starting with a developer learning resource:
This course will allow you to understand all the ideas interactively.
Then download and unzip the installation package to a separate folder and launch the console application.
You will get a working service on port 5002 with the same examples.
See the article https://www.savetodb.com/odatadb/quick-start.htm for details.
In the article, you will also find details on deploying the application on Windows and Linux in various ways.
In general, it will take less than an hour to get the first web application for an existing database.
Feel free to contact us.