[GNUnet-SVN] [taler-schemafuzz] branch master updated: tex details

[gnunet]

This is an automated email from the git hooks/post-receive script.

erwan-ulrich pushed a commit to branch master
in repository schemafuzz.

The following commit(s) were added to refs/heads/master by this push:
     new 69d7cc3  tex details
69d7cc3 is described below

commit 69d7cc31ff343b86af19d8580b4883939475ee84
Author: Feideus <address@hidden>
AuthorDate: Fri Aug 10 10:06:35 2018 +0200

    tex details
---
 Documentation.tex | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/Documentation.tex b/Documentation.tex
index b16c24a..9ec163e 100755
--- a/Documentation.tex
+++ b/Documentation.tex
@@ -142,17 +142,17 @@ The possible modifications that this tool can produce at 
the moment are : % add
                                        \item Increment/Decrement date by 1 
day/minutes depending on the precision of the date
                                        \item Set date to 00/00/0000
                                \end{itemize}
-Obviously, these "abnormal" values might in fact be totally legit in some 
cases. in that case the analyzer (see dedicated section) w
+Obviously, these "abnormal" values might in fact be totally legit in some 
cases. in that case the analyzer 
+will rank the mutation rather poorly, which will lead to this tree path not 
being very likely to be developped further more.
                                \\*
                                \paragraph{Sql handling}
+All the SQL statements are generated within the code. This means that the data 
concerning the current and future state of the mutations have to be very 
precise. Otherwise, the SQL statement is very likely to fail. Sadly, since 
SchemaFuzz only supports postgreSQL, the implemented synthax follow the one of 
postgres
+DBMS. This is already a very big axis for future improvements and will be 
detailled in the dedicated section.
+The statement is built to target the row as precisely as possible, meaning 
that it uses all of the non fuzzed values from the row to avoid updating other 
row accidently. Only the types that can possibly be fuzzed will be used in the 
building of the SQL statement. Since this part of the code is very delicate in 
the sense that it highly depends on an arbitrary large pool of variables from 
various types it is a good bugg provider. 
+                               
                                \paragraph{Injecting}
-SchemaFuzz builds the SQL statement that will be injected in the database. As 
every DBRMS has its own synthax only PostGresSql synta
-The statement is built to target the row as precisely as possible, meaning 
that it uses all of the non fuzzed values from the fuzzed
-
-                               \paragraph{Sql handling}
-                               \paragraph{Injecting}
-                               \paragraph{Do/Undo routine}
                                \paragraph{Special Cases(MutationTransfert)}
+                               \paragraph{Do/Undo routine}
                        \subsubsection{TreeBased data structure}
                                \paragraph{Weight}
                                \paragraph{Path}

-- 
To stop receiving notification emails like this one, please contact
address@hidden