strict mode
Won't the database raise an exception in the event you execute a bad query?
 I did not mean handling exceptions triggered by the RDBMS, that is working OK, seems. I meant strictness in the parsing and processing of model definitions, e.g. the following attribute definition: 

```
    field = CharField(unigue=True)  # misspelled keyword unique
```

At run-time I did not get a warning or exception from peewee, and peewee will 'just' generate code for the RDBMS. The created table is not as intended, since the unique index is missing. The program seems to work allright, at first glance, but duplicate records may (and in my case will) occur in the table. 

I like Peewee. Great job so far. It may be lightweight, but it should do a proper job :-)

To summarize: more strict parsing of the model is really useful and needed. 
 The `kwargs` parameter of a field object's `__init__()` method is being used to populate arbitrary field attributes, so I'm not sure how to add protection against misspellings.
 To clarify, since _anything_ could be a valid keyword argument, I'm not sure how to fix this.
 A bit challenged by coleifer last remark, I decided to have a look at the peewee code myself. I was struck by the small size of the program, really. It looks good, and as such is a good display of the power of the Python language. 

I don't agree that anything could be a valid keyword. Just put all in a dict, and use that dict to check the passed keyword/value pairs. Just by adding a few lines of code to add to the **init** method of the Field class, just before the invocation of the super-method, enables me to signal my misspellings - at least:

```
    for key in kwargs:
            if key not in ['null', 'index', 'unique' .... 'sequence']:
                    print "Error with passed key: " + key
```

I left out a few keywords here in this pseudo-code fragment. Anyway, it should be referencing a constant list declared somewhere in top of the program. I think there are some more places in the code that could benefit of this little construct.

Writing a Model will generate code for the RDBMS of choice, if the create_table() method is called. I noticed that there seems to be no check on the actual response of the RDBMS. See my issue #259, which illustrated that peewee generates a statements for MySQL, but a faulty one, in that particular example. Is there any possiblity to add a sort of 'strictness' switch to peewee? 

This 'strictness' should not only apply to feedback from the RDBMS while generating an index, but also help to avoid misspelled words, e.g. unigue in stead of unique, which was not noticed by me until I discovered that the anticipated index creation was not promoted to the database. 
