git-svn-id: file:///svn/tokudb@3335 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3334 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3327 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3326 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3325 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3324 c7de825b-a66e-492c-adef-691d508d4ae1

{{{
svn merge -r3272:3320 https://svn.tokutek.com/tokudb/tokudb.558
}}}
No conflicts.


git-svn-id: file:///svn/tokudb@3322 c7de825b-a66e-492c-adef-691d508d4ae1

Write leafentry code, and get things to compile.  Make it more compatible with -Wconversion.  Addresses #558.

git-svn-id: file:///svn/tokudb@3270 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3269 c7de825b-a66e-492c-adef-691d508d4ae1

{{{ybt.c}}} was trying to {{{find_db_file}}} after closing the file.  Now it finds the filename first, closes the db, and then unlinks the file.  Fixes #644.

git-svn-id: file:///svn/tokudb@3266 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3265 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3264 c7de825b-a66e-492c-adef-691d508d4ae1

{{{
svn merge -r3229:3230 https://svn.tokutek.com/tokudb/tokudb.558
}}}
and resolved the conflicts.  Now I'll get rid of the 558 branch again.
Addresses #558.


git-svn-id: file:///svn/tokudb@3262 c7de825b-a66e-492c-adef-691d508d4ae1

The order in which the two callbacks is done has changed during pma splitting.    The inter-gpma callback is done first, then the intra-gpma is done.  The test had it backward.  Fixes #641.

git-svn-id: file:///svn/tokudb@3260 c7de825b-a66e-492c-adef-691d508d4ae1

Port of toku__lt_init_full_query to OSX's somewhat broken compiler.

git-svn-id: file:///svn/tokudb@3257 c7de825b-a66e-492c-adef-691d508d4ae1

Lock tree further disentangled from transactions.
Now uses a function to compare txnids all the time instead of direct
integer compare, also removed asserts checking for them to be non 0,
since 0 is a valid TXN id.

git-svn-id: file:///svn/tokudb@3256 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3255 c7de825b-a66e-492c-adef-691d508d4ae1

{{{test-recover3.tdb}}} doesn't crash during recovery now.  (It crashes because it recovered to the wrong state.)  Addresses #558.

git-svn-id: file:///svn/tokudb@3254 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3252 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3250 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3245 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3240 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3238 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3237 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3234 c7de825b-a66e-492c-adef-691d508d4ae1

I did:
{{{
svn merge -r3229:3230 https://svn.tokutek.com/tokudb/tokudb.558
}}}


git-svn-id: file:///svn/tokudb@3231 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3227 c7de825b-a66e-492c-adef-691d508d4ae1

{{{
svn merge -r3061:3225 https://svn.tokutek.com/tokudb/tokudb.558
}}}

Fixes #630.
Addresses #558.


git-svn-id: file:///svn/tokudb@3226 c7de825b-a66e-492c-adef-691d508d4ae1

ignoring the non-fast version of the lock trees

git-svn-id: file:///svn/tokudb@3220 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3219 c7de825b-a66e-492c-adef-691d508d4ae1

Lock escalation for reads.
Also, bugfix with lock escalation for writes, we sometimes forgot to set 
OUT_OF_LOCKS to FALSE

git-svn-id: file:///svn/tokudb@3217 c7de825b-a66e-492c-adef-691d508d4ae1

Range trees now return ranges in sorted order

git-svn-id: file:///svn/tokudb@3189 c7de825b-a66e-492c-adef-691d508d4ae1

Fixed a bug in tokudb.
In a NO_DUP database, if we have a cursor pointing to an element,
and then insert (overwrite) an element with the same key but larger (as per cmp func)
data, then DB_NEXT should NOT return the newly inserted element.. it should
return the element with the next larger key.

The opposite error also existed for DB_PREV.

We rewrite the flag of DB_NEXT/DB_PREV to DB_NEXT_NODUP and DB_PREV_NODUP
when there are no duplicates.

git-svn-id: file:///svn/tokudb@3155 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3154 c7de825b-a66e-492c-adef-691d508d4ae1

We were reading error codes of malloc incorrectly.
errno is not valid unless you know you had an error.

git-svn-id: file:///svn/tokudb@3138 c7de825b-a66e-492c-adef-691d508d4ae1

Fixes memory leak (in a test)

git-svn-id: file:///svn/tokudb@3136 c7de825b-a66e-492c-adef-691d508d4ae1

Merge all of ticket 567 into trunk

git-svn-id: file:///svn/tokudb@3134 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3048 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3041 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@3040 c7de825b-a66e-492c-adef-691d508d4ae1