...
| Name | Type | Bytes |
|---|---|---|
| recordId | String (36 chars) | 108 |
| appVersion | String (48 chars) | 144 |
| phoneInfo | String (48 chars) | 144 |
| uploadDate | String (10 chars) | 30 |
| healthCode | String (36 chars) | 108 |
| externalId | String (128 chars) | 384 |
| dataGroups | String (250 chars) | 750 |
| createdOn | Timestamp | 20 |
| createdOnTimeZone | String (5 chars) | 15 |
| userSharingScope | String (48 chars) | 144 |
| validationErrors | Large Text | 3000 |
| substudyMemberships | String (250 chars) | 750 |
| dayInStudy | Int | 20 |
| rawData | File Handle | 20 |
| rawMetadata | File Handle | 20 |
A few Bridge studies declare study-wide metadata that goes into every table. The current maximum usage of metadata fields is psorcast-validation, which uses 2 timestamp fields and 8 Strings of length 100, which represents 10 columns and 2440 bytes.
Proposed Bridge Schema Limits
| Source | Columns | Bytes |
|---|---|---|
| Common | 1415 | 56375657 |
| Metadata | 20 | 2500 |
| Reserved | 1817 | 58635843 |
| Schema | 100 | 50000 |
| Total | 152 | 64000 |
...