ladybird/Userland/Libraries/LibSQL/CMakeLists.txt

set(SOURCES
    AST/CreateSchema.cpp
    AST/CreateTable.cpp
    AST/Expression.cpp
    AST/Insert.cpp
    AST/Lexer.cpp
    AST/Parser.cpp
    AST/Select.cpp
    AST/SyntaxHighlighter.cpp
    AST/Token.cpp
    BTree.cpp
    BTreeIterator.cpp
    Database.cpp
    HashIndex.cpp
    Heap.cpp
    Index.cpp
    Key.cpp
    Meta.cpp
    Row.cpp
    Serializer.cpp
    SQLClient.cpp
    TreeNode.cpp
    Tuple.cpp
    Value.cpp
    )

set(GENERATED_SOURCES
    ../../Services/SQLServer/SQLClientEndpoint.h
    ../../Services/SQLServer/SQLServerEndpoint.h
    )

serenity_lib(LibSQL sql)
target_link_libraries(LibSQL LibCore LibSyntax)
LibSQL: Introduce a SQL library with a tokenizer LibSQL aims to be a SQLite clone for SerenityOS. Step 1 is creating a tokenizer to lex SQL tokens. This lexer is heavily influenced by the LibJS lexer. 2021-04-18 17:35:40 -04:00			`set(SOURCES`
LibSQL: Invent statement execution machinery and CREATE SCHEMA statement This patch introduces the ability execute parsed SQL statements. The abstract AST Statement node now has a virtual 'execute' method. This method takes a Database object as parameter and returns a SQLResult object. Also introduced here is the CREATE SCHEMA statement. Tables live in a schema, and if no schema is present in a table reference the 'default' schema is implied. This schema is created if it doesn't yet exist when a Database object is created. Finally, as a proof of concept, the CREATE SCHEMA and CREATE TABLE statements received an 'execute' implementation. The CREATE TABLE method is not able to create tables created from SQL queries yet. 2021-06-27 21:32:22 -04:00			`AST/CreateSchema.cpp`
			`AST/CreateTable.cpp`
LibSQL+SQLServer: Bare bones INSERT and SELECT statements This patch provides very basic, bare bones implementations of the INSERT and SELECT statements. They are very limited: - The only variant of the INSERT statement that currently works is SELECT INTO schema.table (column1, column2, ....) VALUES (value11, value21, ...), (value12, value22, ...), ... where the values are literals. - The SELECT statement is even more limited, and is only provided to allow verification of the INSERT statement. The only form implemented is: SELECT * FROM schema.table These statements required a bit of change in the Statement::execute API. Originally execute only received a Database object as parameter. This is not enough; we now pass an ExecutionContext object which contains the Database, the current result set, and the last Tuple read from the database. This object will undoubtedly evolve over time. This API change dragged SQLServer::SQLStatement into the patch. Another API addition is Expression::evaluate. This method is, unsurprisingly, used to evaluate expressions, like the values in the INSERT statement. Finally, a new test file is added: TestSqlStatementExecution, which tests the currently implemented statements. As the number and flavour of implemented statements grows, this test file will probably have to be restructured. 2021-07-19 19:48:46 -04:00			`AST/Expression.cpp`
			`AST/Insert.cpp`
LibSQL: Invent statement execution machinery and CREATE SCHEMA statement This patch introduces the ability execute parsed SQL statements. The abstract AST Statement node now has a virtual 'execute' method. This method takes a Database object as parameter and returns a SQLResult object. Also introduced here is the CREATE SCHEMA statement. Tables live in a schema, and if no schema is present in a table reference the 'default' schema is implied. This schema is created if it doesn't yet exist when a Database object is created. Finally, as a proof of concept, the CREATE SCHEMA and CREATE TABLE statements received an 'execute' implementation. The CREATE TABLE method is not able to create tables created from SQL queries yet. 2021-06-27 21:32:22 -04:00			`AST/Lexer.cpp`
			`AST/Parser.cpp`
LibSQL+SQLServer: Bare bones INSERT and SELECT statements This patch provides very basic, bare bones implementations of the INSERT and SELECT statements. They are very limited: - The only variant of the INSERT statement that currently works is SELECT INTO schema.table (column1, column2, ....) VALUES (value11, value21, ...), (value12, value22, ...), ... where the values are literals. - The SELECT statement is even more limited, and is only provided to allow verification of the INSERT statement. The only form implemented is: SELECT * FROM schema.table These statements required a bit of change in the Statement::execute API. Originally execute only received a Database object as parameter. This is not enough; we now pass an ExecutionContext object which contains the Database, the current result set, and the last Tuple read from the database. This object will undoubtedly evolve over time. This API change dragged SQLServer::SQLStatement into the patch. Another API addition is Expression::evaluate. This method is, unsurprisingly, used to evaluate expressions, like the values in the INSERT statement. Finally, a new test file is added: TestSqlStatementExecution, which tests the currently implemented statements. As the number and flavour of implemented statements grows, this test file will probably have to be restructured. 2021-07-19 19:48:46 -04:00			`AST/Select.cpp`
LibSQL: Invent statement execution machinery and CREATE SCHEMA statement This patch introduces the ability execute parsed SQL statements. The abstract AST Statement node now has a virtual 'execute' method. This method takes a Database object as parameter and returns a SQLResult object. Also introduced here is the CREATE SCHEMA statement. Tables live in a schema, and if no schema is present in a table reference the 'default' schema is implied. This schema is created if it doesn't yet exist when a Database object is created. Finally, as a proof of concept, the CREATE SCHEMA and CREATE TABLE statements received an 'execute' implementation. The CREATE TABLE method is not able to create tables created from SQL queries yet. 2021-06-27 21:32:22 -04:00			`AST/SyntaxHighlighter.cpp`
			`AST/Token.cpp`
			`BTree.cpp`
			`BTreeIterator.cpp`
			`Database.cpp`
			`HashIndex.cpp`
			`Heap.cpp`
			`Index.cpp`
			`Key.cpp`
			`Meta.cpp`
			`Row.cpp`
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-18 20:50:13 -04:00			`Serializer.cpp`
LibSQL+SQLServer: Build SQLServer system service This patch introduces the SQLServer system server. This service is supposed to be the only process/application talking to database storage. This makes things like locking and caching more reliable, easier to implement, and more efficient. In LibSQL we added a client component that does the ugly IPC nitty- gritty for you. All that's needed is setting a number of event handler lambdas and you can connect to databases and execute statements on them. Applications that wish to use this SQLClient class obviously need to link LibSQL and LibIPC. 2021-06-28 21:15:17 -04:00			`SQLClient.cpp`
LibSQL: Invent statement execution machinery and CREATE SCHEMA statement This patch introduces the ability execute parsed SQL statements. The abstract AST Statement node now has a virtual 'execute' method. This method takes a Database object as parameter and returns a SQLResult object. Also introduced here is the CREATE SCHEMA statement. Tables live in a schema, and if no schema is present in a table reference the 'default' schema is implied. This schema is created if it doesn't yet exist when a Database object is created. Finally, as a proof of concept, the CREATE SCHEMA and CREATE TABLE statements received an 'execute' implementation. The CREATE TABLE method is not able to create tables created from SQL queries yet. 2021-06-27 21:32:22 -04:00			`TreeNode.cpp`
			`Tuple.cpp`
			`Value.cpp`
			`)`
LibSQL: Introduce a SQL library with a tokenizer LibSQL aims to be a SQLite clone for SerenityOS. Step 1 is creating a tokenizer to lex SQL tokens. This lexer is heavily influenced by the LibJS lexer. 2021-04-18 17:35:40 -04:00
LibSQL+SQLServer: Build SQLServer system service This patch introduces the SQLServer system server. This service is supposed to be the only process/application talking to database storage. This makes things like locking and caching more reliable, easier to implement, and more efficient. In LibSQL we added a client component that does the ugly IPC nitty- gritty for you. All that's needed is setting a number of event handler lambdas and you can connect to databases and execute statements on them. Applications that wish to use this SQLClient class obviously need to link LibSQL and LibIPC. 2021-06-28 21:15:17 -04:00			`set(GENERATED_SOURCES`
			`../../Services/SQLServer/SQLClientEndpoint.h`
			`../../Services/SQLServer/SQLServerEndpoint.h`
			`)`

LibSQL: Introduce a SQL library with a tokenizer LibSQL aims to be a SQLite clone for SerenityOS. Step 1 is creating a tokenizer to lex SQL tokens. This lexer is heavily influenced by the LibJS lexer. 2021-04-18 17:35:40 -04:00			`serenity_lib(LibSQL sql)`
LibSQL: Add a syntax highlighter 2021-05-08 18:30:18 -07:00			`target_link_libraries(LibSQL LibCore LibSyntax)`