Hi Josh Thanks for your feedback. Here is my quick comment:
> > - The one major feature DeZign has that I didn't see -- at least in my > few minutes of using your free version -- is the ability to partition the > diagram into multiple diagrams. This way, I don't have to have to just > one > enormous visual diagram of the whole schema. Instead, I can work with one > limited area at a time. Perhaps that's what "subject areas" refers to on > your website, but I didn't see any details on that, either on the site or > in the app. > > In Vertabelo there is one diagram for one model. If you want to divide your models into separated areas "subject area" can help. Here is the video about subject area usage https://www.youtube.com/watch?v=a79nEA0FN1M&list=PLghpIrBTN3RIqsePBQOCrVci6GEohtoDD The design decision in this matter was'nt simple. It is a trade-off between full abstraction (models + diagrams) and simplicity. In Vertabelo we generally stand up on simplicity, this way some features known from big desktop toois are not available. > > - The versioning/tagging is very cool. Ultimately, for us, each > incremental update to the model will exist in the context of a specific > GitHub branch and commit, so it'd be nice if there were a direct GitHub > integration so that I could, for example, make a commit in a GitHub > branch, > and then in Vertabelo immediatley tag that commit. It looks like the > current versions are a more subversion-style "linear" track, and that you > would create branches by "Create a New Model From...". Maybe in practice, > that's good enough. > > Your are right. We have a discussion in our team months ago and integration with git is on our roadmap, but priority for it is low. You are the first user who asked about it. Linear track is a design decision and branching can be simulated as you wrote by "Create new model from". We would'nt like to implement full versioning system. > > - When I generate my SQL in DeZign, I often want to generate only a > subset of my model (e.g. all tables in a particular schema), whereas it > appears here I can only generate all SQL at once and filter by type > (table, > indexes, etc.,) but not by table. > > Some other users alse asking about it and it seams reasonable. We consider to add something in this area. > > - It would be nice to divide models by schema. We plan to have > several hundred tables in our model, so we divide them by schema to keep > them organized, whereas it looks like I would need to view all tables > alphabetically. > > You can assign a schema to a table or other object by setting appropriate > additional table property. Of course this can't help in model navigating, but > together with subject areas should be enough. We don't plan to add schema to > the database model as the first class citizen because different database > engines treat schemas in very different ways - so its hard to generalize this > concept. You can also put any ideas/bugs/feature request into our support platform - http://support.vertabelo.com/ - it is easy to track the progress. Regards Jarosław -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
