search for: log_remove

As for splitting a leaf, root is just the leaf, and tree mod log does not apply on leaf, so in this case, we don''t do log_removal. As for splitting a node, the old root is kept as a normal node and we have nicely put records in tree mod log for moving keys and items, so in this case we don''t do that either. As above, insert_new_root can get rid of log_removal. Signed-off-by:

If you look the code carefully, you will see all the tree_mod_alloc() has to use GFP_ATOMIC. However, the original code pass the wrong arg gfp_t in some places, this dosen''t cause any problems, because in the tree_mod_alloc(), it ignores arg gfp_t and just use GFP_ATOMIC directly, this is not good. However, i think we should try best not to allocate with GFP_ATOMIC, so i keep the gfp_t

Hi, I''m using an ActiveRecord::Observer to log users changing data in my application. However, I''ve noted that adding an item to a has_many relationship gets logged, but removing the item does not. That is: @product.users << user is logged, but: @product.users.delete(user) is not. I''ve dug into ActiveRecord and found that the underlying issue is that the

...write_inheritable_array(add_callback.to_sym, [:log_add]) #remove_callback remove_callback = "before_remove_for_#{association.name}" class_inheritable_reader(remove_callback.to_sym) write_inheritable_array(remove_callback.to_sym, [:log_remove]) end } end end#end ClassMethods This works well and the only way I found to do this without: 1) Didn''t want to have to require code in the model. I wanted it to be "smart". 2) Didn''t want to "alias_method" any Rails code. I though...