We weren't testing that a valid key format with an invalid value format
failed.  Add code to test and enhance test_schema02 to check.
The "loadtext" command can reasonably create the database.
Add the "loadtext" command to the help/usage output.
Sort the command parsing switch statement alphabetically.
Wrap the btree cursor operations with code that saves/restores the cursor
key/data information, move the handling of WT_CURSTD_{KEY,VALUE}_{APP,RET}
flags out of the btree code and into the cursor code.   Reference #607.
Restore the copy of the key/value as part of entering the API: the reason is
that when a cursor's key or value are pointing at internal memory (which is
what the RET flag indicates), that memory is only safe while the cursor
keeps a page referenced. As soon as the cursor releases the page (which
happens at the beginning of most operations), it could be evicted and the
memory could become invalid.

Make the test for whether or not a WT_ITEM.data field references inside the
WT_ITEM's allocated memory a bit more complicated: overflow items will have
data fields that point inside the allocated memory, not at the start of it.
Clear "key set" flags in LSM if searches fail.
cur_file.c:268: warning: '__value_data' may be used uninitialized in this function
cur_file.c:268: warning: '__key_data' may be used uninitialized in this function
cur_file.c:268: warning: '__value_size' may be used uninitialized in this function
cur_file.c:268: warning: '__key_size' may be used uninitialized in this function
cur_file.c:268: warning: '__recno' may be used uninitialized in this function
spelling typo
Revert to switching to the APP flags when making a copy of the key/value.  This is required to support the following sequence:

 - set_key
  - KEY_APP flag set
 - search
  - success, RET flags set
 - remove
  - key copied, RET flag stays set
  - deadlock, RET flags cleared
 - retry remove
  - fails: neither KEY_APP or KEY_RET is set

refs #607
Don't clear the key after a cursor remove.
refs #607
Make a copy of the key after a successful remove.
refs #607
Rename cursor flags KEY/VALUE_INT/EXT to clarify that they track whether the key/value points into the tree or out of the tree.
whitespace
When we changed the meaning of the overwrite configuration, we missed
the wt utility's load command.   Change the flag's name, add tests for
the flag to the test suite, make a note in the upgrading docs.
There are four possible states for the WT_PAGE.dsk memory: the WT_PAGE
disk-image is mapped into memory (unmap on page discard), is in allocated
memory (free on page discard), is in memory belonging to a caller (ignore on
page discard), or isn't set at all (ignore on page discard).

We've been trying to figure out which based on the state of WT_PAGE.dsk and
a single flag, and that's not enough.  Use two explicit flags, one for
mapped memory and one for allocated memory, and neither flag is set for the
latter two states.
Rework the documentation & examples to better reflect "overwrite" is
configured on/true by default, and should only be set if you want
non-standard behavior.
fixed signed/unsigned and 32/64 bit compilation warnings.  refs #593