> I think JavaScript would benefit from an in-memory database.
That database would probably look a lot like a JSON object. What are you suggesting, that a global JSON object does not solve? > I think JavaScript would benefit from an in-memory database.
That database would probably look a lot like a JSON object. What are you suggesting, that a global JSON object does not solve?The more structures you have in a given application and the larger those structures become in their schemas the more valuable a uniform storage and retrieval solution becomes.
from cities select state where name='Chicago'
isn't really different from cities.filter(x=>x.name=='Chicago').map(x=>x.state)Its not about what it looks like. Arrays have fancy functional methods, but not object structures. Its more about whether it executes faster and comprises fewer steps to read/write. A real case in my application is get all ports associated with unencrypted sockets associated with servers of a given type and sort the output in a manner chosen by the user. The data in this case is in different unrelated objects whose properties point to each other in various ways by identity, because each server and socket uses hashes for unique identifiers.
- Assigns an immutable ID to the element, even if additional elements are added or removed.
- Returns that element ID when pushing.
Each "table" would be a top-level array item.
As for JOINs, I can think of a few syntax that are already supported, but none that I like. Any ideas?