You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: articles/Intersection/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -139,7 +139,7 @@ We have been testing these approaches on a quite old server with Intel Xeon X567
139
139
140
140
Tables clearly show a dominance of Roaringbitmap approach from the query time and index size perspective. However, these are not the only aspects of data processing. There are certain drawbacks of non-relational approaches that need to be kept in mind if we consider using them:
141
141
142
-
1. Values in an array are not foreign keys. Therefore, referential integrity inside the database has to be maintained by the application.
142
+
1. Values in an array are not foreign keys (<ahref="https://commitfest.postgresql.org/17/1252/">yet</a>). Therefore, referential integrity inside the database has to be maintained by the application.
143
143
2. It can be particularly costly to add new documents into the Roaringbitmap implementation of our database.
144
144
3. It may be difficult to express a different type of query using the ARRAY or Roaringbitmap approach.
0 commit comments