serenity/Userland/Services/SQLServer/SQLServer.ipc

#include <LibSQL/Value.h>

endpoint SQLServer
{
    connect(DeprecatedString name) => (Optional<u64> connection_id)
    prepare_statement(u64 connection_id, DeprecatedString statement) => (Optional<u64> statement_id)
    execute_statement(u64 statement_id, Vector<SQL::Value> placeholder_values) => (Optional<u64> execution_id)
    disconnect(u64 connection_id) => ()
}
SQLServer+SQLStudio+sql: Allow sending placeholder values to SQLServer 2022-12-02 08:17:50 -05:00			`#include <LibSQL/Value.h>`

SQLServer: Remove unnecessary magic number 2021-11-01 15:41:34 +01:00			`endpoint SQLServer`
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			`{`
LibSQL+SQLServer+SQLStudio+sql: Propagate connection errors immediately Currently, when clients connect to SQL server, we inform them of any errors opening the database via an asynchronous IPC. But we already know about these errors before returning from the connect() IPC, so this roundabout propagation is a bit unnecessary. Now if we fail to open the database, we will simply not send back a valid connection ID. Disconnect has a similar story. Rather than disconnecting and invoking an asynchronous IPC to inform the client of the disconnect, make the disconnect() IPC synchronous (because all it does is remove the database from the map of open databases). Further, the only user of this command is the SQL REPL when it wants to connect to a different database, so it makes sense to block it. This did require moving a bit of logic around in the REPL to accommodate this change. 2022-12-03 07:07:42 -05:00			`connect(DeprecatedString name) => (Optional<u64> connection_id)`
LibSQL+SQLServer+SQLStudio+sql: Use proper types for SQL IPC and IDs When storing IDs and sending values over IPC, this changes SQLServer to: 1. Stop using -1 as a nominal "bad" ID. Store the IDs as unsigned, and use Optional in the one place that the IPC needs to indicate an ID was not allocated. 2. Let LibIPC encode/decode enumerations (SQLErrorCode) on our behalf. 3. Use size_t for array sizes. 2022-12-02 16:25:27 -05:00			`prepare_statement(u64 connection_id, DeprecatedString statement) => (Optional<u64> statement_id)`
LibSQL+SQLServer+SQLStudio+sql: Allocate per-statement-execution IDs In order to execute a prepared statement multiple times, and track each execution's results, clients will need to be provided an execution ID. This will create a monotonically increasing ID each time a prepared statement is executed for this purpose. 2022-12-02 17:14:56 -05:00			`execute_statement(u64 statement_id, Vector<SQL::Value> placeholder_values) => (Optional<u64> execution_id)`
LibSQL+SQLServer+SQLStudio+sql: Propagate connection errors immediately Currently, when clients connect to SQL server, we inform them of any errors opening the database via an asynchronous IPC. But we already know about these errors before returning from the connect() IPC, so this roundabout propagation is a bit unnecessary. Now if we fail to open the database, we will simply not send back a valid connection ID. Disconnect has a similar story. Rather than disconnecting and invoking an asynchronous IPC to inform the client of the disconnect, make the disconnect() IPC synchronous (because all it does is remove the database from the map of open databases). Further, the only user of this command is the SQL REPL when it wants to connect to a different database, so it makes sense to block it. This did require moving a bit of logic around in the REPL to accommodate this change. 2022-12-03 07:07:42 -05:00			`disconnect(u64 connection_id) => ()`
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			`}`