Jan de Visser 85a84b0794 LibSQL: Introduce Serializer as a mediator between Heap and client code ... Classes reading and writing to the data heap would communicate directly with the Heap object, and transfer ByteBuffers back and forth with it. This makes things like caching and locking hard. Therefore all data persistence activity will be funneled through a Serializer object which in turn submits it to the Heap. Introducing this unfortunately resulted in a huge amount of churn, in which a number of smaller refactorings got caught up as well.		2021-08-21 22:03:30 +02:00
..
CMakeLists.txt	LibSQL+SQLServer: Build SQLServer system service	2021-07-08 17:55:59 +04:30
TestSqlBtreeIndex.cpp	LibSQL: Introduce Serializer as a mediator between Heap and client code	2021-08-21 22:03:30 +02:00
TestSqlDatabase.cpp	LibSQL: Redesign Value implementation and add new types	2021-08-21 22:03:30 +02:00
TestSqlExpressionParser.cpp	LibSQL: Make lexer and parser more standard SQL compliant	2021-06-24 00:36:53 +02:00
TestSqlHashIndex.cpp	LibSQL: Introduce Serializer as a mediator between Heap and client code	2021-08-21 22:03:30 +02:00
TestSqlStatementExecution.cpp	LibSQL+SQLServer: Bare bones INSERT and SELECT statements	2021-08-21 22:03:30 +02:00
TestSqlStatementParser.cpp	LibSQL: Move Order and Nulls enums from SQL::AST to SQL namespace	2021-07-08 17:55:59 +04:30
TestSqlValueAndTuple.cpp	LibSQL: Introduce Serializer as a mediator between Heap and client code	2021-08-21 22:03:30 +02:00