Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Andrea Ferrandi
    @aferrandi
    It should not be so long to the next version 1.15, with primary keys and foreign keys icons on the UI table headings (#58), sorting of tables (#57) and better messaging (#61). Some testing is needed for #58, because the primary keys metadata format could be database dependent.
    Andrea Ferrandi
    @aferrandi
    It will also fix #59, centralizing the accelerators, thus avoiding confusion with the tabs.
    Andrea Ferrandi
    @aferrandi
    The version 1.15 was released, after some problems with #58 (primary and foreign keys icons in columns), since the snap version of the system did not show the keys when they was displayed as UTF16 characters. So now dbtarzan shows the keys as blue and yellow keys icons, which is actually better.
    Andrea Ferrandi
    @aferrandi
    Issue #64 has been resolved adding an in memory small database (H2) containg only 3 tables connected to each other by foreign keys. A very small database with a very few rows, but enough to make sure that the application continues to work as it should after each change.
    Andrea Ferrandi
    @aferrandi
    I'm doing some refactoring in DBTarzan. The purpose is to simplify the code, mainly the GUI code. It should also allow to increment the amount of code that can be tested.
    Now GUIWorker passes messages to DatabaseTabs and indirectly to Database and TableTabs instead of calling methods, thus largely reducing the amount of boilerplate methods in those classes.
    I'm also trying to reduce the size of TableTabs and BrowsingTable by moving their code to new classes.
    Andrea Ferrandi
    @aferrandi
    Working on 1.18. After the issues #75 (automatic sizing of table columns) and #66 (progress bar), working on the localization of the GUI text (#73). A "global settings" dialog is needed to set the desired language, and will be used also for the database password encryption (#70), to choose if a password is needed and in that case which password.
    Andrea Ferrandi
    @aferrandi
    Released version 1.18 with table columns with width fitting to the content, and multiple UI languages:
    window.png
    Andrea Ferrandi
    @aferrandi
    aferrandi/dbtarzan#70, which was supposed to be solved with version 1.18, was more complicated than what was assumed initially. DBTarzan needs to be able to check that the password is correct, without changing the file format and saving the password in any additional file. Also the transition to the password use must be painless.
    Andrea Ferrandi
    @aferrandi
    For this reason, #70 will be postponed to version 1.19 or 1.20.
    Andrea Ferrandi
    @aferrandi
    After I worked on #77 and #79 (they are in the code), I have been working on #70 for a while. #70 is a task to add security to the application an security is always "olistic", you need to completely finish the task before pushing it to github or the code will not work.
    It seems that I am close to the end with #70, the code is now there, but I'll need some more test before I push the code to github.
    Andrea Ferrandi
    @aferrandi
    Version 1.20 is out. It includes mainly 2 new features:
    Andrea Ferrandi
    @aferrandi
    The additional foreign keys can be very useful.
    It can happen that a database is missing some foreign keys, because the administrators forgot to add them or just don't thing that they are needed.
    But DBTarzan needs the foreign keys to move from one table to the other, so we can just add some "surrogates" that act exactly as foreign keys from the point of view of DBTarzan, but are kept in the local DBTarzan configuration without any changes needed in the database.
    Also, there are JDBC drivers for NoSQL databases. So in theory it is possible to add additional foreign keys to the DBTarzan configuration to be able to move from one table to the other in the NoSQL database, being careful about the size of the tables and the resulting performance.