Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with eav
Search options not deleted
user 276789
Entity-Attribute-Value. A data model with a potentially big number of attributes of which only few apply to a single entity.
1
vote
1
answer
514
views
EAV or JSONB column for dynamic data that needs good indexing
So I see only two ways to handle this:
dynamically create the right indexes for specific fields
store the data in a EAV pattern with columns for different data types like timestamp, int, ... … But everyone seems to strongly advise against EAV every time this comes up, so I'm not entirely sure how problematic this solution would be.
Am I missing any solutions here? …
- 115