Permalink
Browse files

Merge pull request #1 from pwnall/patch-1

fix typo in Readme
  • Loading branch information...
barunio committed Feb 22, 2012
2 parents 1aaa57a + 204bfaf commit 05da52d0d1a39e6f7d31bc517acc554d183c0d01
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.md
View
@@ -69,7 +69,7 @@ Now let's review what we've done.
* Instead of `imageable_type` and `imageable_id` columns in the pictures table, we've created explicit columns for the `employee_id` and `product_id`
* The `add_polymorphic_constraints` call takes care of all of the database constraints you need, without you needing to worry about sql! Specifically it:
* Creates foreign key relationships in the database as specified. So in this example, we have specified that the `employee_id` column in the `pictures` table should have a foreign key constraint with the `id` column of the `employees` table.
- * Creates appropriate triggers in our database that make sure that exactly on or the other of `employee_id` or `poduct_id` are specified for a given record. An exception will be raised if you try to save a database record that contains both or none of them.
+ * Creates appropriate triggers in our database that make sure that exactly on or the other of `employee_id` or `product_id` are specified for a given record. An exception will be raised if you try to save a database record that contains both or none of them.
* **Options for migrations**: There are options to customize the foreign keys generated by Polymorpheus and add uniqueness constraints. For more info on this, [read the wiki entry](https://github.com/wegowise/polymorpheus/wiki/Migration-options).
## Model definitions

0 comments on commit 05da52d

Please sign in to comment.