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

50 lines
1.1 KiB
Rust
Raw Normal View History

Large update to code to convert Golang to Rust
2022-01-13 17:36:41 +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;
Large update to code to convert Golang to Rust
2022-01-13 17:36:41 +00:00
use crate::sql::object::Object;
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;
Large update to code to convert Golang to Rust
2022-01-13 17:36:41 +00:00
use crate::sql::value::Value;
impl Value {
Convert all processing code to async
2022-01-14 08:12:56 +00:00
pub async fn object(
&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,
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
path: &[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
) -> Result<(), Error> {
Large update to code to convert Golang to Rust
2022-01-13 17:36:41 +00:00
let val = Value::from(Object::default());
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
self.set(ctx, opt, txn, path, val).await
Large update to code to convert Golang to Rust
2022-01-13 17:36:41 +00:00
}
}
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
#[cfg(test)]
mod tests {
use super::*;
use crate::dbs::test::mock;
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::idiom::Idiom;
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::test::Parse;
#[tokio::test]
async fn object_none() {
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
let (ctx, opt, txn) = mock().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
let idi = Idiom::default();
let mut val = Value::parse("{ test: { other: null, something: 123 } }");
let res = Value::parse("{}");
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
val.object(&ctx, &opt, &txn, &idi).await.unwrap();
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
assert_eq!(res, val);
}
#[tokio::test]
async fn object_path() {
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
let (ctx, opt, txn) = mock().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
let idi = Idiom::parse("test");
let mut val = Value::parse("{ test: { other: null, something: 123 } }");
let res = Value::parse("{ test: {} }");
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
val.object(&ctx, &opt, &txn, &idi).await.unwrap();
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
assert_eq!(res, val);
}
}
Reference in a new issue Copy permalink