#267 Use set (sorted by std::greater) instead of unordered_set for new_ids
This commit is contained in:
parent
d4c7c97f4c
commit
a5d6bcb825
1 changed files with 5 additions and 5 deletions
|
|
@ -29,15 +29,15 @@
|
||||||
namespace graphene { namespace db {
|
namespace graphene { namespace db {
|
||||||
|
|
||||||
using std::unordered_map;
|
using std::unordered_map;
|
||||||
using fc::flat_set;
|
using fc::flat_set;
|
||||||
class object_database;
|
class object_database;
|
||||||
|
|
||||||
struct undo_state
|
struct undo_state
|
||||||
{
|
{
|
||||||
unordered_map<object_id_type, unique_ptr<object> > old_values;
|
unordered_map<object_id_type, unique_ptr<object> > old_values;
|
||||||
unordered_map<object_id_type, object_id_type> old_index_next_ids;
|
unordered_map<object_id_type, object_id_type> old_index_next_ids;
|
||||||
std::unordered_set<object_id_type> new_ids;
|
std::set<object_id_type, std::greater<object_id_type> > new_ids;
|
||||||
unordered_map<object_id_type, unique_ptr<object> > removed;
|
unordered_map<object_id_type, unique_ptr<object> > removed;
|
||||||
};
|
};
|
||||||
|
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue