Revision: 3169
Author: [email protected]
Date: Tue Nov 17 10:49:00 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/power-architect/source/detail?r=3169
Modified:
/wiki/CriticsFunctionality.wiki
=======================================
--- /wiki/CriticsFunctionality.wiki Tue Nov 17 09:47:26 2009
+++ /wiki/CriticsFunctionality.wiki Tue Nov 17 10:49:00 2009
@@ -5,11 +5,11 @@
The idea behind the Critics feature is to have a monitor of your data
model that will notify the user of errors, mistakes, and bad practices in
their data model. A simple analogy would be like how spell-checking works
in modern word processors.
= Motivation =
- * A vocal group of users dislike some of the automatic data modelling
features of the Architect. (For example, how can get hijacked for foreign
key creation) Adding Critics would allow this automation to be disabled,
and make the Architect easier to work with for different data modelling
strategies.
+ * A vocal group of users dislike some of the automatic data modelling
features of the Architect. (For example, how columns can get hijacked for
foreign key creation) Adding Critics would allow this automation to be
disabled, and make the Architect easier to work with for different data
modelling strategies.
* Currently, one of the less pleasant User Interface aspects of the
Architect is the QuickFix functionality when you try to forward engineer a
data model into a platform, but your data model violates some rules for
that platform. Implementing the Critics feature can allow us to completely
remove the QuickFix feature.
- * There are a number of active bugs that are blocked by the
implementation of the Critics functionality.
+ * There are a number of active bugs that are blocked by the
implementation of the Critics functionality. These are mostly warning the
user about incompatible or incorrect data models, and we believe the
Critics feature is the most elegant and least obtrusive method of dealing
with this.
* Bug 997 - Check for out-of-range precision and scale
* Bug 1439 - Check for invalid or empty column mappings for
relationships
* Bug 1536 - Warn user about using incompatible index types for the
given storage engine (MySQL)
