Our Vision

The Oracle DBMS has come a long way. It is a mature, highly scalable and manageable product. And as such it is the platform of choice for coding business applications. Against the grain we advocate a database centric approach to application development. The arguments behind this, and the approach of how to do this are explained in detail by Toon Koppelaars at The Helsinki Declaration blog.

In a database centric approach the database design (aka datamodel) on top of which the application is built, is the center of the universe. Integral part of a database design are its business rules; which in relational database theory map to data integrity constraints.

Data quality is about ensuring that the database only holds data that conforms to the business rules that you have specified. And here's where RuleGen comes into play: we generate all necessary PL/SQL code for enforcing the integrity constraints. And since this enforcement is implemented at the database level, in a separate code-layer, that can be independently managed from all other application code, and always fires when transactions are issued against the database, you can rest assured that no developer can build code that compromises the data quality.



News & Events

Check out our new blog on triggers here.

Or follow us:

RuleGen 3.0 released

With the open architecture of release 3.0, RuleGen has set the path for the future. Improved code generation, transparent code deployment, and separation of design and runtime, are some of the key highlights of this new release.

Available now: AM4DP

Click to see book on Amazon

A great textbook about data integrity constraints in relational databases. This book describes the key concepts on which RuleGen is based. Click image to see reviews at Amazon, or here for quotes found on internet.