Nexus memory tables are not limited in their functionality when compared to on-disk tables, like some other memory tables are. In fact, the *only* difference when compared to an on-disk table is that a memory table is not written to disk when updates occur.

This means:

The table belongs to a database and can therefore be part of  transactions  with other (mem)tables in that same database.
The table data is kept at the server and transferred to/from the  clients  via transports. The transports only come into play with external servers,  not with an embedded serverengine. But the principle is the same even in  this situation. The server(engine) handles the physical data, be it a  file  or just some memory blocks.
Memory tables can have different scopes (sql statement, database, global).
When using an exposed server the same table can be used by different clients.
Home | Site Contents | Documentation | NexusDB Manual V4 | Architecture and Concepts | NexusDB Concepts