Release of ModelRight 3.5 Supporting PostgreSQL

Princeton, NJ -- April 2, 2009: ModelRight, Inc., a privately owned software company based in Princeton, New Jersey, has released a beta version of its flagship product, ModelRight 3.5, supporting PostgreSQL. ModelRight delivers a fresh new approach to data modeling providing

in-depth database support, full-cycle data modeling and robust, user friendly features all at an affordable price.

ModelRight 3.5 for PostgreSQL supports all functionality of the Professional version of ModelRight including: Reverse Engineer, Forward Engineer, Database Compare, Alter Script Generation, and support for several notations (IE, IDEF1X and Barker). Additionally, this release provides specific features for PostgreSQL including:

“We are very excited to announce our beta release of ModelRight 3.5 supporting PostgreSQL,” stated Tim Guinther, President & Founder of ModelRight, Inc. “We have received many inquires from our user base to support PostgreSQL. We listened to them, and delivered the PostgreSQL capabilities in our latest release,” added Guinther. If you are interested in testing ModelRight 3.5 for PostgreSQL and receiving this open release, please contact ModelRight at sales@modelright.com or call us at 609-423-9297.

ModelRight has distinguished itself from other data modeling tools for its top 10 unique features and reasonable price. The cost of ModelRight ranges from $245 - $895 per seat license and there is also a Free Community Version of ModelRight 3.5 for PostgreSQL.

#

About ModelRight, Inc.

ModelRight, Inc. is a privately owned software company based in Princeton, NJ. ModelRight provides effective database modeling tools supporting various databases. ModelRight, the company’s flagship product, streamlines the design process for database professionals and software developers, empowering them to design, visualize and document the database they are building or using. Learn more about ModelRight at www.modelright.com.

This post has been migrated from a previous version of the PostgreSQL
website. We apologise for any formatting issues caused by the migration.