noth/surrealpatch
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
surrealpatch/lib/src/sql/value/merge.rs

27 lines
530 B
Rust
Raw Normal View History

Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
use crate::dbs::Options;
use crate::dbs::Runtime;
Only pass transaction when processing queries Instead of passing the executor instance, we only need to pass the current transaction which is to be used for processing and running any queries.
2022-02-15 01:00:30 +00:00
use crate::dbs::Transaction;
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
use crate::err::Error;
Improve performance with query path analysis Instead of creating a new Vec<_> for every embedded path part, we now use a reference when calling get/set/del on a value’s data. This means we aren’t creating and copying the Vec items each and every time we traverse down a path.
2022-02-22 19:05:58 +00:00
use crate::sql::part::Part;
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
use crate::sql::value::Value;
impl Value {
pub async fn merge(
&mut self,
ctx: &Runtime,
Don't store selected NS and DB on executor
2022-02-06 21:06:52 +00:00
opt: &Options,
Switch to asynchronous owned mutex locks in underlying kv storage
2022-02-15 03:33:16 +00:00
txn: &Transaction,
Allow any value in CONTENT / REPLACE / MERGE clauses
2022-02-13 23:39:10 +00:00
val: &Value,
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
) -> Result<(), Error> {
Only pass transaction when processing queries Instead of passing the executor instance, we only need to pass the current transaction which is to be used for processing and running any queries.
2022-02-15 01:00:30 +00:00
match val.compute(ctx, opt, txn, Some(self)).await? {
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
Value::Object(v) => {
for (k, v) in v.value.into_iter() {
Improve performance with query path analysis Instead of creating a new Vec<_> for every embedded path part, we now use a reference when calling get/set/del on a value’s data. This means we aren’t creating and copying the Vec items each and every time we traverse down a path.
2022-02-22 19:05:58 +00:00
self.set(ctx, opt, txn, &[Part::from(k)], v).await?;
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
}
Ok(())
}
Allow any value in CONTENT / REPLACE / MERGE clauses
2022-02-13 23:39:10 +00:00
_ => Ok(()),
Return a Result from async methods on Value Instead of silently failing, the async methods on a Value for getting, setting, and updating the value, now return a Result. This means we can chain the awaited result using the ? operator.
2022-01-20 23:00:57 +00:00
}
}
}
Reference in a new issue Copy permalink