Lines Matching full:they
147 # particular, read-only transactions do not take locks, so they do
149 # taking locks, they also do not abort, so retry loops are not needed.
151 # Transactions may only read/write data in a single database. They
214 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
228 # Snapshot transactions do not take locks. Instead, they work by
230 # timestamp. Since they do not acquire locks, they do not block
234 # transactions never abort. They can fail if the chosen read
255 # or read-write transaction, because they are able to execute far
280 # prefix of the global transaction history: they observe
283 # transactions with a larger commit timestamp. They will block until
291 # timestamp. As a result, they execute slightly faster than the
308 # reads, even if they use the same staleness bound, can execute at
318 # reads. However, they are typically able to return fresher
332 # as "version GC". By default, version GC reclaims versions after they
439 # mutations are applied atomically, in the order they appear in
708 # particular, read-only transactions do not take locks, so they do
710 # taking locks, they also do not abort, so retry loops are not needed.
712 # Transactions may only read/write data in a single database. They
775 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
789 # Snapshot transactions do not take locks. Instead, they work by
791 # timestamp. Since they do not acquire locks, they do not block
795 # transactions never abort. They can fail if the chosen read
816 # or read-write transaction, because they are able to execute far
841 # prefix of the global transaction history: they observe
844 # transactions with a larger commit timestamp. They will block until
852 # timestamp. As a result, they execute slightly faster than the
869 # reads, even if they use the same staleness bound, can execute at
879 # reads. However, they are typically able to return fresher
893 # as "version GC". By default, version GC reclaims versions after they
1089 # particular, read-only transactions do not take locks, so they do
1091 # taking locks, they also do not abort, so retry loops are not needed.
1093 # Transactions may only read/write data in a single database. They
1156 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
1170 # Snapshot transactions do not take locks. Instead, they work by
1172 # timestamp. Since they do not acquire locks, they do not block
1176 # transactions never abort. They can fail if the chosen read
1197 # or read-write transaction, because they are able to execute far
1222 # prefix of the global transaction history: they observe
1225 # transactions with a larger commit timestamp. They will block until
1233 # timestamp. As a result, they execute slightly faster than the
1250 # reads, even if they use the same staleness bound, can execute at
1260 # reads. However, they are typically able to return fresher
1274 # as "version GC". By default, version GC reclaims versions after they
1365 # particular, read-only transactions do not take locks, so they do
1367 # taking locks, they also do not abort, so retry loops are not needed.
1369 # Transactions may only read/write data in a single database. They
1432 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
1446 # Snapshot transactions do not take locks. Instead, they work by
1448 # timestamp. Since they do not acquire locks, they do not block
1452 # transactions never abort. They can fail if the chosen read
1473 # or read-write transaction, because they are able to execute far
1498 # prefix of the global transaction history: they observe
1501 # transactions with a larger commit timestamp. They will block until
1509 # timestamp. As a result, they execute slightly faster than the
1526 # reads, even if they use the same staleness bound, can execute at
1536 # reads. However, they are typically able to return fresher
1550 # as "version GC". By default, version GC reclaims versions after they
1855 # particular, read-only transactions do not take locks, so they do
1857 # taking locks, they also do not abort, so retry loops are not needed.
1859 # Transactions may only read/write data in a single database. They
1922 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
1936 # Snapshot transactions do not take locks. Instead, they work by
1938 # timestamp. Since they do not acquire locks, they do not block
1942 # transactions never abort. They can fail if the chosen read
1963 # or read-write transaction, because they are able to execute far
1988 # prefix of the global transaction history: they observe
1991 # transactions with a larger commit timestamp. They will block until
1999 # timestamp. As a result, they execute slightly faster than the
2016 # reads, even if they use the same staleness bound, can execute at
2026 # reads. However, they are typically able to return fresher
2040 # as "version GC". By default, version GC reclaims versions after they
2131 # particular, read-only transactions do not take locks, so they do
2133 # taking locks, they also do not abort, so retry loops are not needed.
2135 # Transactions may only read/write data in a single database. They
2198 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
2212 # Snapshot transactions do not take locks. Instead, they work by
2214 # timestamp. Since they do not acquire locks, they do not block
2218 # transactions never abort. They can fail if the chosen read
2239 # or read-write transaction, because they are able to execute far
2264 # prefix of the global transaction history: they observe
2267 # transactions with a larger commit timestamp. They will block until
2275 # timestamp. As a result, they execute slightly faster than the
2292 # reads, even if they use the same staleness bound, can execute at
2302 # reads. However, they are typically able to return fresher
2316 # as "version GC". By default, version GC reclaims versions after they
2477 # # because they are strings.
2481 # # because they are lists. Recursively, the last and first elements
2482 # # of the inner lists are merged because they are strings.
2729 # particular, read-only transactions do not take locks, so they do
2731 # taking locks, they also do not abort, so retry loops are not needed.
2733 # Transactions may only read/write data in a single database. They
2796 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
2810 # Snapshot transactions do not take locks. Instead, they work by
2812 # timestamp. Since they do not acquire locks, they do not block
2816 # transactions never abort. They can fail if the chosen read
2837 # or read-write transaction, because they are able to execute far
2862 # prefix of the global transaction history: they observe
2865 # transactions with a larger commit timestamp. They will block until
2873 # timestamp. As a result, they execute slightly faster than the
2890 # reads, even if they use the same staleness bound, can execute at
2900 # reads. However, they are typically able to return fresher
2914 # as "version GC". By default, version GC reclaims versions after they
3005 # particular, read-only transactions do not take locks, so they do
3007 # taking locks, they also do not abort, so retry loops are not needed.
3009 # Transactions may only read/write data in a single database. They
3072 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
3086 # Snapshot transactions do not take locks. Instead, they work by
3088 # timestamp. Since they do not acquire locks, they do not block
3092 # transactions never abort. They can fail if the chosen read
3113 # or read-write transaction, because they are able to execute far
3138 # prefix of the global transaction history: they observe
3141 # transactions with a larger commit timestamp. They will block until
3149 # timestamp. As a result, they execute slightly faster than the
3166 # reads, even if they use the same staleness bound, can execute at
3176 # reads. However, they are typically able to return fresher
3190 # as "version GC". By default, version GC reclaims versions after they
3643 # particular, read-only transactions do not take locks, so they do
3645 # taking locks, they also do not abort, so retry loops are not needed.
3647 # Transactions may only read/write data in a single database. They
3710 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
3724 # Snapshot transactions do not take locks. Instead, they work by
3726 # timestamp. Since they do not acquire locks, they do not block
3730 # transactions never abort. They can fail if the chosen read
3751 # or read-write transaction, because they are able to execute far
3776 # prefix of the global transaction history: they observe
3779 # transactions with a larger commit timestamp. They will block until
3787 # timestamp. As a result, they execute slightly faster than the
3804 # reads, even if they use the same staleness bound, can execute at
3814 # reads. However, they are typically able to return fresher
3828 # as "version GC". By default, version GC reclaims versions after they
3919 # particular, read-only transactions do not take locks, so they do
3921 # taking locks, they also do not abort, so retry loops are not needed.
3923 # Transactions may only read/write data in a single database. They
3986 # seconds. Idle transactions can be aborted by Cloud Spanner so that they
4000 # Snapshot transactions do not take locks. Instead, they work by
4002 # timestamp. Since they do not acquire locks, they do not block
4006 # transactions never abort. They can fail if the chosen read
4027 # or read-write transaction, because they are able to execute far
4052 # prefix of the global transaction history: they observe
4055 # transactions with a larger commit timestamp. They will block until
4063 # timestamp. As a result, they execute slightly faster than the
4080 # reads, even if they use the same staleness bound, can execute at
4090 # reads. However, they are typically able to return fresher
4104 # as "version GC". By default, version GC reclaims versions after they
4370 # # because they are strings.
4374 # # because they are lists. Recursively, the last and first elements
4375 # # of the inner lists are merged because they are strings.