You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`filename`|`TEXT`| The filename of the attachment |
64
-
|`media_type`|`TEXT`| The media type of the attachment |
65
-
|`state`|`INTEGER`| The state of the attachment, one of `AttachmentState` enum values |
66
-
|`timestamp`|`INTEGER`| The timestamp of the last update to the attachment record |
67
-
|`size`|`INTEGER`| The size of the attachment in bytes |
68
-
|`has_synced`|`INTEGER`| Internal tracker which tracks if the attachment has ever been synced. This is used for caching/archiving purposes. |
69
-
|`meta_data`|`TEXT`| Any extra meta data for the attachment. JSON is usually a good choice. |
48
+
The `createAttachmentTable` function defines the `local-only` attachment state storage table. See the [Implementation Details](#implementation-details) section for more details.
70
49
71
50
#### Steps to Implement
72
51
@@ -153,7 +132,7 @@ try await queue.saveFile(
153
132
}
154
133
```
155
134
156
-
#### Handling Errors
135
+
#### (Optional) Handling Errors
157
136
158
137
The attachment queue automatically retries failed sync operations. Retries continue indefinitely until success. A `SyncErrorHandler` can be provided to the `AttachmentQueue` constructor. This handler provides methods invoked on a remote sync exception. The handler can return a Boolean indicating if the attachment sync should be retried or archived.
0 commit comments