mirror of
https://github.com/Wisser/Jailer.git
synced 2026-05-08 02:30:18 -05:00
updated tutorial
This commit is contained in:
+5
-15
@@ -304,26 +304,16 @@
|
||||
<br />
|
||||
But why are there also statements for all other employees?<br />
|
||||
<br />
|
||||
Let Jailer explain why:<br />
|
||||
Click on "EMPLOYEE" in the "Rows per Table" overview. This displays all process steps leading to additional employee records.<br>
|
||||
<br />
|
||||
<img src="exporting-data-Dateien/screen10.png" /><br />
|
||||
<img src="dbs12_sel.gif" /><br />
|
||||
<br />
|
||||
<br />
|
||||
Open the <span style=
|
||||
"font-family: monospace;">Explain.log</span>:<br />
|
||||
<br />
|
||||
<img style="width: 280px; height: 196px;" alt="" src=
|
||||
"dbs13.gif" /><br />
|
||||
<br />
|
||||
<img src="exporting-data-Dateien/screen12.png" /><br />
|
||||
<br />
|
||||
The data of Adams and James, for example, has been exported,
|
||||
because Scott (7788) is Adams (7876) boss and James (7900) and
|
||||
Adams are both classified in the same salary-grade.<br />
|
||||
As you can see, among other things, all employees who are assigned to the same department as SCOTT are exported.<br />
|
||||
<br />
|
||||
|
||||
<h4>Step 4. Export employee Scott (restricted)<br /></h4>Exporting
|
||||
an employee requires to export his boss and department too!
|
||||
an employee requires to export his boss and department too.
|
||||
Otherwise the set of exported entities would not be consistent (due
|
||||
to the dependencies based on foreign key constraints). No
|
||||
constraint prevents us from excluding the salary-grade and the
|
||||
@@ -390,7 +380,7 @@
|
||||
<td style=
|
||||
"vertical-align: top; background-color: rgb(202, 225, 235);"
|
||||
colspan="2"><span style="font-family: monospace;">--
|
||||
generated by Jailer at Sat May 03 12:38:33 CEST 2008
|
||||
generated by Jailer at Sat May 03 12:38:33 CEST 2019
|
||||
from wisser@desktop<br />
|
||||
--<br />
|
||||
-- extraction model: EMPLOYEE where NAME='SCOTT'
|
||||
|
||||
Reference in New Issue
Block a user