diff --git a/manual/docs/Getting started - Exporting classes - Export options.php b/manual/docs/Getting started - Exporting classes - Export options.php
new file mode 100644
index 000000000..d6331c936
--- /dev/null
+++ b/manual/docs/Getting started - Exporting classes - Export options.php	
@@ -0,0 +1,11 @@
+<code type='php'>
+// export everything, table definitions and constraints
+
+$manager->setAttribute(Doctrine::ATTR_EXPORT, Doctrine::EXPORT_ALL);
+
+// export classes without constraints
+
+$manager->setAttribute(Doctrine::ATTR_EXPORT, Doctrine::EXPORT_TABLES ^ 
+                                              Doctrine::EXPORT_CONSTRAINTS);
+
+</code>
diff --git a/manual/docs/Object relational mapping - Constraints and validators - Notnull.php b/manual/docs/Object relational mapping - Constraints and validators - Notnull.php
index 57bb08f88..ca1a38a06 100644
--- a/manual/docs/Object relational mapping - Constraints and validators - Notnull.php	
+++ b/manual/docs/Object relational mapping - Constraints and validators - Notnull.php	
@@ -17,3 +17,7 @@ class User extends Doctrine_Record
 When this class gets exported to database the following Sql statement would get executed (in Mysql):
 
 CREATE TABLE user (name VARCHAR(200) NOT NULL, PRIMARY KEY(name))
+
+The notnull constraint also acts as an application level validator. This means that if Doctrine validators are turned on, Doctrine will automatically check that specified columns do not contain null values when saved.
+
+If those columns happen to contain null values Doctrine_Validator_Exception is raised.