DataTransaction.write — Queue a numeric slice write.
tf = DataTransaction.write(tx, arrayName, sliceSpec, values) retains the supplied slice and values in an open transaction; commit applies the write to the named stored array.
Syntax
tf = DataTransaction.write(tx, arrayName, sliceSpec, values)Inputs
tx- Type
Any- Required
- Yes
- Default
- —
- Description
- Managed DataTransaction receiver.
name- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Array name.
sliceSpec- Type
Any- Required
- Yes
- Default
- —
- Description
- Cell slice specification or ':' text.
values- Type
Any- Required
- Yes
- Default
- —
- Description
- Numeric values to persist.
Returns
tf- Type
LogicalArray- Description
- Logical result.
Errors
RUNMAT:Data:Error- When
- A Dataset family receiver, argument, manifest, payload, or filesystem operation fails.
- Message
data: operation failed
RunMat:data:ManifestConflict- When
- A transaction's expected manifest sequence no longer matches the stored manifest.
- Message
data: manifest conflict
RunMat:data:TransactionNotFound- When
- The transaction is absent from the process-local registry.
- Message
data: transaction not found
Validation and ownership
The queue call validates the managed transaction and array name, but slice geometry, declared dtype, and values are checked during commit. Values may be resident until the commit path gathers them; no GPU execution or publication is promised by this queue call.
Example
Queue a slice write
schema = struct(); schema.arrays.sample = struct('dtype', 'uint64', 'shape', [1 2]);
ds = data.create('tx-write.data', schema);
tx = Dataset.begin(ds);
tf = DataTransaction.write(tx, 'sample', {':', 2}, uint64(8));
DataTransaction.commit(tx);
arr = Dataset.array(ds, 'sample');Using DataTransaction.write with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how DataTransaction.write changes the result.
Run a small DataTransaction.write example, explain the result, then change one input and compare the output.
FAQ
Does queueing write array chunks?⌄
No. Commit writes fresh array revisions. A failed publication can leave unreferenced revision files, but does not overwrite previously referenced chunks.
Related Io functions
Data
commit · data.copy · data.create · data.delete · data.exists · data.export · data.import · data.inspect · data.list · data.move · data.open · DataArray.chunk_shape · DataArray.codec · DataArray.dtype · DataArray.fill · DataArray.name · DataArray.rank · DataArray.read · DataArray.resize · DataArray.shape · DataArray.write · Dataset.array · Dataset.arrays · Dataset.attrs · Dataset.begin · Dataset.get_attr · Dataset.has_array · Dataset.id · Dataset.path · Dataset.refresh · Dataset.set_attr · Dataset.set_attrs · Dataset.snapshot · Dataset.version · DataTransaction.abort · DataTransaction.commit · DataTransaction.create_array · DataTransaction.delete_array · DataTransaction.fill · DataTransaction.id · DataTransaction.resize · DataTransaction.set_attr · DataTransaction.set_attrs · DataTransaction.status
Repl Fs
addpath · cd · copyfile · delete · dir · exist · fileattrib · fileparts · filesep · fullfile · genpath · getenv · getpref · isenv · isfile · isfolder · ispref · ls · matlabroot · memmapfile · memmapfile.subsasgn · memmapfile.subsref · mkdir · movefile · open · opentoline · path · pathsep · pcode · pwd · readstruct · rehash · restoredefaultpath · rmdir · rmpath · run · savepath · setenv · setpref · system · tempdir · tempname · uigetdir · uigetfile · uiputfile · unsetenv · userpath · what · winqueryreg · xmlread · xmlwrite
Tabular
arrayDatastore · csvread · csvwrite · detectImportOptions · dlmread · dlmwrite · fileDatastore · getvaropts · parquetDatastore · parquetinfo · parquetread · readcell · readmatrix · readtable · readtimetable · setvaropts · setvartype · spreadsheetImportOptions · writecell · writematrix · writetable · writetimetable · xlsread · xlswrite
Filetext
fclose · feof · fgetl · fgets · fileread · filewrite · fopen · fprintf · fread · frewind · fwrite · readlines · writelines
Import
Json
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how DataTransaction.write is executed, line by line, in Rust.
- View the source for DataTransaction.write in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.