ORM Designer

ORM Designer Description

ORM Designer is a simple utility meant for ERD databases, that provides you with full support for ORM frameworks based on any structured language. ORM Designer was created to replace kilobytes of text definitions with easy-to-use graphical interface.Thanks to a very flexible design almost any ORM framework with definitions stored in a markup language can be fully supported. Currently supported ORM frameworks are PHP Propel and PHP Doctrine. Symfony web framework in combination with Propel and Doctrine is also supported. ORM Designer supports framework specific options like object behaviors, inheritance, I18N (internationalization) or versioning. You can organize the model into regions to keep related tables easy to find. Data model can be separated into plugin or module files and reuse these parts in another project. ORM Designer has all its internal definitions stored in a human readable XML format. Which means you can always easily check and compare changes made to the model when committing to versioning system and also you can make post processing scripts of database model.You can also download Portable ORM Designer. Here are some key features of "ORM Designer":Model Manipulation:ORM Designer has some features known from IDEs (Integrated Development Environments). Developers will be familiar with a project tree. It's a tree representation of database model with regions, columns, indexes and foreign keys. Project tree is not only another visualization of database model. it can be used to run all model management tasks. ORM Designer also has advanced searching tools which are able to search through relations, columns, regions and tables. Database model can be printed in a predefined zoom level or to fit model to a number of papers.Files and Serialization:ORM Designer is based on a very flexible XML document which is used to store data model definitions and visualization data. Thanks to the open XML format it is very easy to extend ORM Designer with another features, customize it for a new ORM framework or use stored data for post processing tasks. ORM Designer can be configured to save all definitions into one file or to use separate files for each module and also to keep data definitions and visualization data in separate files. ORM Designer contains advanced merging which means you can import parts of other projects or ORM definitions into an existing ORM Designer project.ORM Frameworks:Any framework with its definitions stored in a markup language (XML or YAML) or another structured document might be fully supported by ORM Designer. ORM Designer can read from and write into native ORM framework format. ORM framework specific features like inheritance, translatable tables, cascading deletes, behaviours etc. can be defined through attributes on each data model object. Also column types can be defined for each ORM framework. More attributes can be extended with user defined definitions.Custom Object Properties:ORM framework support in ORM Designer is defined in human readable XML documents. All database model objects properties can be customized for ORM framework. Object properties can have simple values of scalar types. For example boolean values (set column as primary key or auto increment) or numbers (string length). ORM frameworks extend regular databases with advanced features: versioning, translatable tables, application cascade deletes, inheritance etc. ORM Designer contains complex object properties. You can select columns to be translated, or tables to be versioned.Programming Practices:ORM Designer has support for best programming practicies in web projects. You can benefit from separating database model into multiple files which is useful for plugins or modules. Visualization data are related to a module. Position of tables, relations and relation visualization is stored into module file and used once imported into other project. ORM framework definitions exported from ORM Designer are unified and can be compared on commit for changes. Another great feature you would appreciate if using versioning systems (Subversion, CVS etc.) is separation of database model definitions and visualization. When comparing on commit, you can check only for changes in database model. Requirements:1Ghz CPU512MB Ram Limitations:14 days trialNag screen What's New in This Release: [ read full changelog ]New automatic application update system (New!)Added 'Add MN association' button to entity editor (New!)New many-to-many validator - don't allow to use same entity as mn-entity and owner/inverse entity (New!)MN wizard - don't allow use single mn entity multiple timesRemoved duplicity message "Please enter full project file name" from project-editor validationFixed occasional crash when creating new several associations through entity -> new associationFixed crash when removing association which uses field which is indexed by some indexNew callstack tracking method for unhandled exceptionsFixed alphabetical ordering of entities in association wizardFixed drawing issue when a new association/inheritance is created and source/destination entity is changed in wizard.Entity dialog - commit entity name when creating/editing association or inheritanceFixed crash after removing last field in entity followed by add new field to same position �.You can free download ORM Designer from Softpedia now.