0c7fd0a23d
Previously, interactive execution and --exec used two models for how a failed
command would impact other commands in the execution.
As an example, consider:
fdb> set foo bar ; set bar f\00 ; set baz foo
In interactive mode, this had the effect of {foo=bar, baz=foo}.
In --exec mode, this had the effect of {foo=bar}.
With this change, both now have the effect of {foo=bar}. This is achieved by
prefixing the last parsed command, which is the one that had the error, with a
fake "parse_error" token.
The execution of this would now look like:
ERROR: malformed escape sequence
>>> set foo bar
ERROR: Command failed to completely parse.
ERROR: Not running partial or malformed command: set bar
Which indicates how much execution occurred and where it halted, identically in
both modes of execution.
|
||
|---|---|---|
| bindings | ||
| build | ||
| fdbbackup | ||
| fdbcli | ||
| fdbclient | ||
| fdbmonitor | ||
| fdbrpc | ||
| fdbserver | ||
| fdbservice | ||
| flow | ||
| layers | ||
| packaging | ||
| recipes | ||
| tests | ||
| .gitignore | ||
| ACKNOWLEDGEMENTS | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| foundationdb.sln | ||
| versions.target | ||
README.md
FoundationDB
FoundationDB is a distributed database designed to handle large volumes of structured data across clusters of commodity servers. It organizes data as an ordered key-value store and employs ACID transactions for all operations. It is especially well-suited for read/write workloads but also has excellent performance for write-intensive workloads. Users interact with the database using API language binding.