summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar cehteh <cehteh@web>2014-03-26 18:55:41 +0000
committerGravatar admin <admin@branchable.com>2014-03-26 18:55:41 +0000
commite9271fa1f34b3b515daf3b1be3560016c40a4b6f (patch)
tree8616b1e2ac146a35ce206129f88e77ef1103ed8c
parent511a3852cc6a66f674296f062c3d5a670dc9a1ce (diff)
Added a comment
-rw-r--r--doc/forum/view_from_numeric_values/comment_3_7879a11cc9767cdaac14f9993182dc25._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/view_from_numeric_values/comment_3_7879a11cc9767cdaac14f9993182dc25._comment b/doc/forum/view_from_numeric_values/comment_3_7879a11cc9767cdaac14f9993182dc25._comment
new file mode 100644
index 000000000..da6dded17
--- /dev/null
+++ b/doc/forum/view_from_numeric_values/comment_3_7879a11cc9767cdaac14f9993182dc25._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="cehteh"
+ ip="217.8.62.137"
+ subject="comment 3"
+ date="2014-03-26T18:55:41Z"
+ content="""
+I'm a little bit worried about the potential to reinvent SQL, badly. ;)
+
+As shown in your example, once you have ranges, it's natural to also want disjunctions, and then probably parenthesized expressions, and suddenly things are very complicated.
+
+Also, it's important that views remain reversable, so that committing a moved file in a view can unambiguously calculate the new metadata for it. I think that quickly becomes hard when adding these complications.
+
+"""]]