Tommy van der Vorst
Tommy van der Vorst
Currently, a node can choose whether to 'replay' SQL transactions on top of the database engine, and select only those tables that it is interested in. The query history however...
Prevent the following: ```` SELECT id, id FROM foo; SELECT a AS id, b AS id FROM foo; ```` This is not currently an issue, but will be at some...
When more than one table is involved in a statement, column names can be ambiguous: ```` SELECT * FROM answers LEFT JOIN questions ON qid = id; ```` The above...
When index
Not really supported by SQLite (in the sense that we need to do a backup, then DROP+CREATE, the restore of the data).
See [SQLite documentation](https://sqlite.org/foreignkeys.html). Most importantly, creation of foreign keys needs to be supported for the `CREATE TABLE` statement: ```` CREATE TABLE album( albumartist TEXT, albumname TEXT, albumcover BINARY, PRIMARY KEY(albumartist,...
Perhaps even allow clients to specify which transactions are to be included (N confirmations required, up to `queueSize`).
When you execute a query in the web client without the required privileges, nothing happens. The client should show a message. Because permissions are checked at runtime (and depend on...