Added a comment
authoryarikoptic <yarikoptic@web>
Mon, 14 Jun 2021 16:23:41 +0000 (16:23 +0000)
committeradmin <admin@branchable.com>
Mon, 14 Jun 2021 16:23:41 +0000 (16:23 +0000)
doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment [new file with mode: 0644]

diff --git a/doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment b/doc/bugs/significant_performance_regression_impacting_datal/comment_27_db91e10d0bea246686ba2241b348e67d._comment
new file mode 100644 (file)
index 0000000..e1c5cfe
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 27"
+ date="2021-06-14T16:23:41Z"
+ content="""
+FWIW, without having a clear idea on code logic/data structures, it smells a bit like somewhere may be it could be `any` vs current `all` operation/check (in case of `add` at least) if needed just to test if there is already a path with a given key, and assuming that DB doesn't require a full rewrite of all `path` entries if a new path added for the key.
+"""]]