0xDBE 1.0 EAP 143.1301 is Out

omething fresh to start this new day—latest 0xDBE EAP build, loaded with bugfixes and improvements. And, its looks have changed too, because we just rebranded the entire company!

Splash

Apart from visual changes, we added native introspection for Sybase. Introspection became more accurate and fast. Among other things now you can see table check constraints and triggers.

Sybase

The Modify Table window acquired some new options:

  • Choose what you want to do finally: apply changes to the database, or open generated code in the text editor. If you are editing existing DDL via this window, you can replace it.
  • Create new keys or indices just from the context menu of the column. Or it can be several columns if you select them with the Ctrl/? pressed.
  • Dedicated tab for keys lets you manage unique keys of the table.

Modify

Check out the new website, and don’t forget to send us your feedback via our issue tracker.

_

0xDBE team

This entry was posted in EAP and tagged , . Bookmark the permalink.

5 Responses to 0xDBE 1.0 EAP 143.1301 is Out

  1. Ivan says:

    thanx guys, i like your new 0xDBE EAP build and waiting for release version

  2. Roy says:

    I thought this product was going to be renamed. I don’t think anyone even knows how to pronounce the current name.

  3. Charles Wheeler says:

    So I noticed the new version has an expiration date on it. What will happen when that date hits? Will I be forced to install a new version, or buy a license?

  4. Rymson Balentien says:

    I love 0xDBE and I’ve used it quite a lot this past year, submitting bugs and feature requests whenever I felt it was appropriate, and I want to congratulate you on your v1 release! That said I’m not sure yet I feel as 0xDBE was ready to go live..We are still missing important schema information within the tool (triggers and constraints being the most important). I’m also not sure if the text-only explain plan cuts it, as the ‘raw desc’ column which sometimes contains useful information is unreadable, as it contains too much information (SQLSERVER). Are these features still being worked on? I guess I’ll sit 0xDBE out until january 9th, when my current install expires and see what to do from there. The only issue is that I can’t see myself working with SSMS anymore either.. :)

Leave a Reply

Your email address will not be published. Required fields are marked *