Make the Vector copy constructor for mismatched inline sizes explicit.

Source/modules/indexeddb/IDBObjectStore.cpp

Index: Source/modules/indexeddb/IDBObjectStore.cpp
diff --git a/Source/modules/indexeddb/IDBObjectStore.cpp b/Source/modules/indexeddb/IDBObjectStore.cpp
index 8f6b4ae18ea3e23b55196b426ef67cfdd821d4a1..f712fffbf04c794978e1f71c96e50e44cedaa63c 100644
--- a/Source/modules/indexeddb/IDBObjectStore.cpp
+++ b/Source/modules/indexeddb/IDBObjectStore.cpp
@@ -340,11 +340,11 @@ private:
             Vector<IDBObjectStore::IndexKeys, 1> indexKeysList;

[jsbell, 2013/09/11 15:44:02]

Given that this just results in copies for passing in as const references
(below), I don't see any benefit in constructing with an inline capacity here.
We should switch this to just Vector<IDBObjectStore::IndexKeys> and revert the
two changes below.

             indexKeysList.append(indexKeys);
 
-            m_databaseBackend->setIndexKeys(m_transactionId, m_objectStoreId, primaryKey, indexIds, indexKeysList);
+            m_databaseBackend->setIndexKeys(m_transactionId, m_objectStoreId, primaryKey, Vector<int64_t>(indexIds), Vector<IDBObjectStore::IndexKeys>(indexKeysList));
         } else {
             // Now that we are done indexing, tell the backend to go
             // back to processing tasks of type NormalTask.
-            m_databaseBackend->setIndexesReady(m_transactionId, m_objectStoreId, indexIds);
+            m_databaseBackend->setIndexesReady(m_transactionId, m_objectStoreId, Vector<int64_t>(indexIds));
             m_databaseBackend.clear();
         }