Skip to content

DataDigger 20

Compare
Choose a tag to compare
@patrickTingen patrickTingen released this 22 Oct 17:36
· 3 commits to 15a1f82c776523e67581f6cd5023d7d125e4ceb5 since this release

Version 20 has been released. Thanks to the DataDigger testing team, a brand new version is ready for you.

Load data

Yes, you can now load data. For the time being you can only load XML files, but if this works well (read: all bugs gone) I will expand this to also work with regular .d and .csv files. You can load files by pressing CTRL-L, clicking the button at the bottom of the screen or by simply dragging the xml file onto the DataDigger

The import process is both new and complicated. And thus might contain some bugs. If you encounter strange issues or bugs please let me know.

Favorites

The favorites section has ben improved. It was already in the previous version but less prominent, while I think it is a really useful feature. The table browse now has its own tabs to switch between the regular list of tables and a list of favorites. You can add or remove a table to the favorites by pressing the star in the right down corner. This star is filled when the table is a favorite or non-filled when not. See above images.

Auto refresh data browse

The data browse can be automatically refreshed. Below the data browse you will find a button and a combo to select the refresh speed. This can be useful for tables that are in progress in a batch process. I am still a bit uncertain whether this should be in the DataDigger. I’d like to hear your opinion on this.

Edit data

The edit data screen now has some extra features for editing data, like a date picker or capitalization functions. See the toolbar at the top of the edit window

Create a .df file, and more

Right-click on a table and among other options you will see the option to create the .df file for that table. In the same menu you can find the option to create a clone database, thus a database with the same structure, but – obviously – empty. You can use this to quickly test out some database changes when you cannot do that on your central database.