17%
03.08.2023
atomically and consistently across all the involved nodes.
Here's a simple example of a transaction that involves updating the prices of two books:
BEGIN;
UPDATE books SET price = price * 0.9 WHERE title
17%
01.08.2019
.
Listing 4
Registry Configuration
01 version: 0.1
02 log:
03 fields:
04 service: registry
05 storage:
06 filesystem:
07 rootdirectory: /var/lib/registry
08 http:
09
17%
29.09.2020
_On_Hours 0x0032 097 097 000 Old_age Always - 12441
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 1482
177 Wear_Leveling_Count 0x0013 098
17%
02.06.2020
optimizer = tf.keras.optimizers.RMSprop(0.001)
11 model.compile(loss='mean_squared_error',
12 optimizer=optimizer,
13 metrics=['mean_absolute_error', 'mean_squared_error'])
The model is shown
17%
09.08.2015
.translation embeddedmap;
09
10 create class Relation extends E;
11 create property Relation.from date;
12
13 create class Appear extends E;
14 create property Appear.chapter embeddedlist integer
15
16 insert into Person
17%
05.12.2019
-created
09 - event: comment-added
10 comment: (?i)^(Patch Set [0-9]+:)?( [\w\\+-]*)*(\n\n)?\s*RECHECK
11 success:
12 gerrit:
13 # return to Gerrit Verified+1
14 Verified: 1
15
17%
08.10.2015
the version number 5.0.10018.0
. This development is all the more interesting, given that the installation directory still goes by the name v1.0; it will probably keep this name for all time for reasons
17%
13.12.2018
Modules xm_gelf
09
10
11 # Use for windows vista/2008 and higher:
12 modules in the_msvistalog
13
14 # Use for windows Windows XP/2000/2003:
15 # Modules in_mseventlog
16
17
17%
14.08.2017
-Agent: curl/7.51.0
08 > Accept: */*
09 >
10 < HTTP/1.1 200 OK
11 < Content-Type: application/json
12 < Content-Length: 382
13 < X-Content-Type-Options: nosniff
14 < Server: WEBrick/1.3.1 (Ruby/2
17%
29.09.2020
.168.2.17",
04 "visible": true,
05 "color": "green",
06 "user": "root"
07 },
08 "web server": {
09 "address": "192.168.2.4",
10 "visible": true,
11 "color": "rgb(100, 200, 0)",
12
