EAR-Database.md

@@ -78,19 +78,6 @@ Additionally, if EAR was compiled in a system with GPUs (or with the GPU flag ma
 
 ### From EAR 4.2 to 4.3
 
-To add support for workflows, a new field was added to several tables to allow their accounting:
-```
-ALTER TABLE Jobs ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
-ALTER TABLE Jobs DROP PRIMARY KEY, ADD PRIMARY KEY (job_id, step_id, local_id);
-```
-```
-ALTER TABLE Applications ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
-ALTER TABLE Applications DROP PRIMARY KEY, ADD PRIMARY KEY (job_id, step_id, local_id);
-```
-```
-ALTER TABLE Loops ADD COLUMN local_id INT UNSIGNED NOT NULL AFTER step_id;
-```
-
 Three new fields corresponding to L1, L2 and L3 cache misses have been added to the signatures.
 
 > **NOTE** This change only applies to the databases that have been created with the extended application signature (i.e. they have the FLOPS, instructions and cycles counters in their signatures).
@@ -101,6 +88,7 @@ ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI,
 ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses,
 ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses;
 ```
+
 ```
 ALTER TABLE Learning_signatures
 ADD COLUMN L1_misses BIGINT UNSIGNED AFTER perc_MPI,
@@ -108,14 +96,9 @@ ADD COLUMN L2_misses BIGINT UNSIGNED AFTER L1_misses,
 ADD COLUMN L3_misses BIGINT UNSIGNED AFTER L2_misses;
 ```
 
-
 ### From EAR 4.1 to 4.2
 
-A field in the Events table had its name changed to be more generic. One can do that with EITHER of the following commands:
-
-```
-ALTER TABLE Events RENAME COLUMN freq TO value;
-```
+A field in the Events table had its name changed to be more generic and its type changed to unsigned:
 
 ```
 ALTER TABLE Events CHANGE freq value INT unsigned;
@@ -178,8 +161,8 @@ EAR's database contains several tables, as described [here](#tables). Each table
 
 ### Jobs
 
-* <span dir="">id: Job id given by the scheduler (for example SLURM\_JOBID).</span>
-* <span dir="">step\_id: step id given by the scheduler.</span>
+* <span dir="">id: Job id given by the scheduler (for example SLURM_JOBID).</span>
+* <span dir="">step_id: step id given by the scheduler.</span>
 * user_id: the linux username that executed the job.
 * app_id: the application/job name as given by the scheduler (not necessarily the executable’s name)
 * start_time: timestamp of the job’s\[.step\] start