diff options
author | Michael Cahill <michael.cahill@wiredtiger.com> | 2011-03-04 09:46:05 +1100 |
---|---|---|
committer | Michael Cahill <michael.cahill@wiredtiger.com> | 2011-03-04 09:46:05 +1100 |
commit | 316ad3cfc5df44f86217f5e55f3549dd2595c504 (patch) | |
tree | 2f8017fc15c804fb81f16fdde755f6d53a4a6eb5 /src/btree/bt_ovfl.c | |
parent | e98a18869d799645ce38478fc887bbe41cfa30e1 (diff) | |
download | mongo-316ad3cfc5df44f86217f5e55f3549dd2595c504.tar.gz |
Make "WT_ITEM" the public name.
Diffstat (limited to 'src/btree/bt_ovfl.c')
-rw-r--r-- | src/btree/bt_ovfl.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/btree/bt_ovfl.c b/src/btree/bt_ovfl.c index 676cfe7feed..f4ceb1ebac3 100644 --- a/src/btree/bt_ovfl.c +++ b/src/btree/bt_ovfl.c @@ -46,7 +46,7 @@ __wt_ovfl_in(SESSION *session, WT_OVFL *ovfl, WT_SCRATCH *store) * buffer and so should be fast, but it's still not a good thing. If * it ever becomes a problem, then we either have to pass the fact that * it's a "page" back to our caller and let them deal with the offset, - * or add a new field to the WT_DATAITEM that flags the start of the allocated + * or add a new field to the WT_ITEM that flags the start of the allocated * buffer, instead of using the "data" field to indicate both the start * of the data and the start of the allocated memory. * @@ -59,7 +59,7 @@ __wt_ovfl_in(SESSION *session, WT_OVFL *ovfl, WT_SCRATCH *store) /* Read the page. */ WT_RET(__wt_disk_read(session, (void *)store->item.data, ovfl->addr, size)); - /* Copy the actual data in the WT_DATAITEM down to the start of the data. */ + /* Copy the actual data in the WT_ITEM down to the start of the data. */ (void)memmove((void *)store->item.data, (uint8_t *)store->item.data + WT_PAGE_DISK_SIZE, ovfl->size); store->item.size = ovfl->size; |