surrealpatch/lib/src/sql/value/first.rs

use crate::dbs::Options;
use crate::dbs::Runtime;
use crate::dbs::Transaction;
use crate::err::Error;
use crate::sql::part::Part;
use crate::sql::value::Value;

impl Value {
	pub async fn first(
		&self,
		ctx: &Runtime,
		opt: &Options,
		txn: &Transaction,
	) -> Result<Self, Error> {
		self.get(ctx, opt, txn, &[Part::First]).await
	}
}
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::part::Part;`
			`use crate::sql::value::Value;`

			`impl 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			`pub async fn first(`
			`&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,`
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<Self, 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			`self.get(ctx, opt, txn, &[Part::First]).await`
Large update to code to convert Golang to Rust 2022-01-13 17:36:41 +00:00			`}`
			`}`